Spring Integration framework provides Kryo Codec implementations as an alternative for Java (de)serialization. When Kryo is configured with default options, all unregistered classes are resolved on demand. This leads to the "deserialization gadgets" exploit when provided data contains malicious code for execution during deserialization. In order to protect against this type of attack, Kryo can be configured to require a set of trusted classes for (de)serialization. Spring Integration should be proactive against blocking unknown "deserialization gadgets" when configuring Kryo in code.
References
Link | Resource |
---|---|
https://tanzu.vmware.com/security/cve-2020-5413 | Vendor Advisory |
https://www.oracle.com//security-alerts/cpujul2021.html | Patch Third Party Advisory |
https://www.oracle.com/security-alerts/cpuApr2021.html | Patch Third Party Advisory |
https://www.oracle.com/security-alerts/cpuapr2022.html | Patch Third Party Advisory |
https://www.oracle.com/security-alerts/cpuoct2021.html | Patch Third Party Advisory |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
History
No history.
Information
Published : 2020-07-31 20:15
Updated : 2024-02-28 17:47
NVD link : CVE-2020-5413
Mitre link : CVE-2020-5413
CVE.ORG link : CVE-2020-5413
JSON object : View
Products Affected
vmware
- spring_integration
oracle
- banking_credit_facilities_process_management
- banking_supply_chain_finance
- flexcube_private_banking
- retail_customer_management_and_segmentation_foundation
- banking_virtual_account_management
- retail_merchandising_system
- banking_corporate_lending_process_management
CWE
CWE-502
Deserialization of Untrusted Data