by Kastro
Paper/Archive/CVE-2020-5413

CVE-2020-5413

Spring by VMware Spring Integration — Kryo Configuration Allows Code Execution with Unknown "Serialization Gadgets"

EPSS 4%CVSS 9.8
critical.is priorityof 100
48
CVSS 9.8 (NVD)9.8 / 10 × 3029.4Not in CISA KEV+300.0EPSS percentile 91.3.913 × 2018.3No public exploit+100.0SSVC exploitation: unknown+100.0
Description · from the CVE record

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.

Affected

ProductAffectedFixed inSource
Spring Integration4.3 – < v4.3.23.RELEASEv4.3.23.RELEASECNA
Spring Integration5.1 – < v5.1.12.RELEASEv5.1.12.RELEASECNA
Spring Integration5.2 – < v5.2.8.RELEASEv5.2.8.RELEASECNA
Spring Integration5.3 – < v5.3.2.RELEASEv5.3.2.RELEASECNA

Scores by source

NVD9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

References

reftanzu.vmware.com/security/cve-2020-5413reforacle.com/security-alerts/cpuApr2021.htmlreforacle.com//security-alerts/cpujul2021.htmlreforacle.com/security-alerts/cpuoct2021.htmlreforacle.com/security-alerts/cpuapr2022.html