vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2020-5413

Kryo Configuration Allows Code Execution with Unknown "Serialization Gadgets"

CRITICAL
9.8
CVSS Score
Published: July 31, 2020 at 07:40 PM UTC
Updated: June 17, 2026 at 03:21 AM UTC
9 products affected across 3 vendorsFlexcube Private BankingRetail Customer Management and Segmentation FoundationRetail Merchandising System

Using Spring Integration by Spring by VMware?

Get instant alerts when new vulnerabilities affect Spring Integration - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
CRITICAL9.8
Exploit prediction
EPSS 4%

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Banking Corporate Lending Process Management· Oracle
95%
14.2.014.3.014.5.0
Banking Credit Facilities Process Management· Oracle
95%
14.2.014.3.014.5.0
Banking Supply Chain Finance· Oracle
95%
14.2.014.3.014.5.0
Banking Virtual Account Management· Oracle
95%
14.2.014.3.014.5.0
Flexcube Private Banking· Oracle
95%
12.0.012.1.0
Retail Customer Management and Segmentation Foundation· Oracledrupal
95%
16.0 ≤ v ≤ 19.0
Retail Merchandising System· Oracle
95%
16.0.3
Spring Integration· VMware
95%
4.3.0 ≤ v ≤ 4.3.225.1.0 ≤ v ≤ 5.1.115.2.0 ≤ v ≤ 5.2.75.3.0 ≤ v ≤ 5.3.1
Spring Integration· Spring by VMware
60%
4.3 ≤ v < v4.3.23.RELEASE5.1 ≤ v < v5.1.12.RELEASE5.2 ≤ v < v5.2.8.RELEASE5.3 ≤ v < v5.3.2.RELEASE4.35.15.25.3
Affected range stops below v4.3.23.RELEASE, so it looks safe — our inference, not a vendor statement
Affected range stops below v5.1.12.RELEASE, so it looks safe — our inference, not a vendor statement
Affected range stops below v5.2.8.RELEASE, so it looks safe — our inference, not a vendor statement
Affected range stops below v5.3.2.RELEASE, so it looks safe — our inference, not a vendor statement

References (5)

x_refsource_CONFIRMVendor Advisory
Source: [email protected]
https://tanzu.vmware.com/security/cve-2020-5413
x_refsource_MISCPatchThird Party Advisory
Source: [email protected]
https://www.oracle.com//security-alerts/cpujul2021.html
x_refsource_MISCPatchThird Party Advisory
Source: [email protected]
https://www.oracle.com/security-alerts/cpuApr2021.html
x_refsource_MISCPatchThird Party Advisory
Source: [email protected]
https://www.oracle.com/security-alerts/cpuapr2022.html
x_refsource_MISCPatchThird Party Advisory
Source: [email protected]
https://www.oracle.com/security-alerts/cpuoct2021.html

CVSS

9.8CRITICAL[email protected]
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-502

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card