Kryo Configuration Allows Code Execution with Unknown "Serialization Gadgets"
CVE-2020-5413

9.8CRITICAL

Key Information:

Vendor

Spring By Vmware

Status
Spring Integration
Vendor
CVE Published:
31 July 2020

What is CVE-2020-5413?

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 Version(s)

Spring Integration 4.3

Spring Integration 5.1

Spring Integration 5.2

References

https://tanzu.vmware.com/security/cve-2020-5413
x_refsource_CONFIRM
https://www.oracle.com/security-alerts/cpuApr2021.html
x_refsource_MISC
https://www.oracle.com//security-alerts/cpujul2021.html
x_refsource_MISC

CVSS V3.1

Score:
9.8
Severity:
CRITICAL
Confidentiality:
High
Integrity:
High
Availability:
High
Attack Vector:
Network
Attack Complexity:
Low
Privileges Required:
None
User Interaction:
None
Scope:
Unchanged

Timeline

  • Vulnerability published

  • Vulnerability Reserved

.
CVE-2020-5413 : Kryo Configuration Allows Code Execution with Unknown "Serialization Gadgets"