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 |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: pivotal
Published: 2020-07-23T00:00:00
Updated: 2022-04-19T23:23:07
Reserved: 2020-01-03T00:00:00
Link: CVE-2020-5413
JSON object: View
NVD Information
Status : Analyzed
Published: 2020-07-31T20:15:13.017
Modified: 2022-05-12T15:01:30.230
Link: CVE-2020-5413
JSON object: View
Redhat Information
No data.
CWE