CVE-2020-5413
Description
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.
Risk Information
Base Score
9.8
MODERATE
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score
Exploitation Probability
2.178
Associated Vulnerability
| Vulnerability | OS Platform |
|---|---|
| Vulnerabilities CVE-2020-5413 are fixed in Spring-integration-core 4.3.23 | Windows |
| Vulnerabilities CVE-2020-5413 are fixed in Spring-integration-core 5.3.2 | Windows |
| Vulnerabilities CVE-2020-5413 are fixed in Spring-integration-core 5.1.12 | Windows |
| Vulnerabilities CVE-2020-5413 are fixed in Spring-integration-core 5.2.8 | Windows |
| Vulnerabilities CVE-2020-5413 are fixed in Spring-integration-core for Linux 4.3.23 | Linux |
| Vulnerabilities CVE-2020-5413 are fixed in Spring-integration-core for Linux 5.3.2 | Linux |
| Vulnerabilities CVE-2020-5413 are fixed in Spring-integration-core for Linux 5.1.12 | Linux |
| Vulnerabilities CVE-2020-5413 are fixed in Spring-integration-core for Linux 5.2.8 | Linux |
Patch Details
No records foundReferences
https://nvd.nist.gov/vuln/detail/CVE-2023-1234
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-1234