Skip to content

Code execution in Spring Integration

Critical severity GitHub Reviewed Published Aug 5, 2020 to the GitHub Advisory Database • Updated Feb 1, 2023

Package

maven org.springframework.integration:spring-integration-core (Maven)

Affected versions

>= 4.3.0, < 4.3.23
>= 5.3.0, < 5.3.2
>= 5.1.0, < 5.1.12
>= 5.2.0, < 5.2.8

Patched versions

4.3.23
5.3.2
5.1.12
5.2.8

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.

References

Published by the National Vulnerability Database Jul 31, 2020
Reviewed Aug 3, 2020
Published to the GitHub Advisory Database Aug 5, 2020
Last updated Feb 1, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.348%
(72nd percentile)

Weaknesses

CVE ID

CVE-2020-5413

GHSA ID

GHSA-86qr-9vqc-pgc6

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.