Spring IntegrationFramework / library · VMware
CVE-2020-5413
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSpring 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisThe application rebuilds objects from attacker-supplied serialized data, and the act of rebuilding can trigger dangerous code paths. In many runtimes this leads straight to remote code execution. The durable fix is to avoid deserializing untrusted input — or to use a strict, type-limited format with integrity checks.
General guidance for the deserialization of untrusted data class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Spring IntegrationFramework / library
>= 4.3.0, <= 4.3.22>= 5.1.0, <= 5.1.11>= 5.2.0, <= 5.2.7>= 5.3.0, <= 5.3.1= 14.2.0= 14.3.0= 14.5.0= 14.2.0= 14.3.0= 14.5.0= 14.2.0= 14.3.0= 14.5.0= 14.2.0= 14.3.0= 14.5.0= 12.0.0= 12.1.0>= 16.0, <= 19.0= 16.0.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedSpring Integration 4.3.23+ / 5.1.12+ / 5.2.8+ / 5.3.2+ (or later stable releases); Oracle July 2021 CPU for banking products
- 1. Identify the Spring Integration version in use by examining project dependencies (e.g., in pom.xml, build.gradle)
- 2. For Spring Integration 4.3.x: upgrade to version 4.3.23 or later
- 3. For Spring Integration 5.1.x: upgrade to version 5.1.12 or later
- 4. For Spring Integration 5.2.x: upgrade to version 5.2.8 or later
- 5. For Spring Integration 5.3.x: upgrade to version 5.3.2 or later
- 6. After upgrading, verify that the application still functions correctly with the new version
- 7. For Oracle Banking products (Corporate Lending, Credit Facilities, Supply Chain Finance, Virtual Account Management, Flexcube Private Banking, Retail CMS Foundation, Retail Merchandising): apply the Oracle July 2021 Critical Patch Update from https://www.oracle.com/security-alerts/cpujul2021.html
Generated from the published advisory — verify against the referenced sources before acting.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5413 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-5413 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data