What’s Vulnerable › Vulnerabilities

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

• Severity: critical (CVSS 9.8 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 4.4% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2020-07-31 · updated 2026-06-17
• Weakness: CWE-502

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.

Affected products

• Oracle Banking Corporate Lending Process Management: 14.2.0, 14.3.0, 14.5.0
• Oracle Banking Credit Facilities Process Management: 14.2.0, 14.3.0, 14.5.0
• Oracle Banking Supply Chain Finance: 14.2.0, 14.3.0, 14.5.0
• Oracle Corporation Banking Virtual Account Management: 14.2.0, 14.3.0, 14.5.0
• Oracle Corporation FLEXCUBE Private Banking: 12.0.0, 12.1.0
• Oracle Corporation Retail Customer Management and Segmentation Foundation: from 16.0 through 19.0
• Oracle Corporation Retail Merchandising System: 16.0.3
• Spring Integration: from 4.3.0 through 4.3.22; from 5.1.0 through 5.1.11; from 5.2.0 through 5.2.7; from 5.3.0 through 5.3.1
• Spring Integration: from 4.3 before v4.3.23.RELEASE; from 5.1 before v5.1.12.RELEASE; from 5.2 before v5.2.8.RELEASE; from 5.3 before v5.3.2.RELEASE — fixed in v4.3.23.RELEASE, v5.1.12.RELEASE, v5.2.8.RELEASE, v5.3.2.RELEASE

How to fix

Upgrade to a fixed version: Spring Integration v4.3.23.RELEASE, v5.1.12.RELEASE, v5.2.8.RELEASE, v5.3.2.RELEASE. Check the vendor advisory for mitigations.

References

• https://tanzu.vmware.com/security/cve-2020-5413
• https://www.oracle.com//security-alerts/cpujul2021.html
• https://www.oracle.com/security-alerts/cpuApr2021.html
• https://www.oracle.com/security-alerts/cpuapr2022.html
• https://www.oracle.com/security-alerts/cpuoct2021.html
• https://tanzu.vmware.com/security/cve-2020-5413
• https://www.oracle.com//security-alerts/cpujul2021.html
• https://www.oracle.com/security-alerts/cpuApr2021.html
• https://www.oracle.com/security-alerts/cpuapr2022.html
• https://www.oracle.com/security-alerts/cpuoct2021.html

Get alerted when CVE-2020-5413 or the next vulnerability affects your stack