CVE-2020-5413 — Code execution in...

CRITICAL

Code execution in Spring Integration

Published August 5, 2020Updated November 8, 2023Source: osv

Summary

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.

Advisory Timeline

First published August 5, 2020 (2259 days ago).
Last revised November 8, 2023 — 1190 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Maven

Update org.springframework.integration:spring-integration-core to 5.1.12 or later

<!-- Update pom.xml dependency version to 5.1.12 for org.springframework.integration:spring-integration-core -->

Maven

Update org.springframework.integration:spring-integration-core to 4.3.23 or later

<!-- Update pom.xml dependency version to 4.3.23 for org.springframework.integration:spring-integration-core -->

Maven

Update org.springframework.integration:spring-integration-core to 5.2.8 or later

<!-- Update pom.xml dependency version to 5.2.8 for org.springframework.integration:spring-integration-core -->

Maven

Update org.springframework.integration:spring-integration-core to 5.3.2 or later

<!-- Update pom.xml dependency version to 5.3.2 for org.springframework.integration:spring-integration-core -->

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (4)

Affects 1 ecosystem: maven (1).

Package	Ecosystem	Affected	Fixed In
org.springframework.integration:spring-integration-core	maven	5.1.0.RELEASE, 5.1.1.RELEASE, 5.1.10.RELEASE, 5.1.11.RELEASE (+8 more)	5.1.12
org.springframework.integration:spring-integration-core	maven	4.3.0.RELEASE, 4.3.1.RELEASE, 4.3.10.RELEASE, 4.3.11.RELEASE (+18 more)	4.3.23
org.springframework.integration:spring-integration-core	maven	5.2.0.RELEASE, 5.2.1.RELEASE, 5.2.2.RELEASE, 5.2.3.RELEASE (+4 more)	5.2.8
org.springframework.integration:spring-integration-core	maven	5.3.0.RELEASE, 5.3.1.RELEASE	5.3.2

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

CWE-502
Deserialization of Untrusted DataMITRE

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 9.8 score means for each attack dimension.

Attack Vector

Network

Attack Complexity

Low

Privileges Required

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

References

Frequently Asked Questions

What is CVE-2020-5413?: Code execution in Spring Integration This vulnerability has been assigned a severity rating of CRITICAL (CVSS score: 9.8/10).
How do I check if my project is affected by CVE-2020-5413?: CVE-2020-5413 affects org.springframework.integration:spring-integration-core. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2020-5413 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score

9.8

Exploitation is straightforward and causes maximum impact. Patch immediately.

Also Known As

GHSA-86qr-9vqc-pgc6

Related CVEs

CVE-2026-107726
CRITICAL
Hazelcast allows arbitrary member memory access by low-privileged client
CVE-2026-107282
CRITICAL
AsyncHttpClient: Replay to a different host sends the original host request and credentials to the new host

More Maven advisories

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies