GHSA-86qr-9vqc-pgc6
Code execution in Spring Integration
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| Maven | org.springframework.integration:spring-integration-core | >= 4.3.0, < 4.3.23 | 4.3.23 |
| Maven | org.springframework.integration:spring-integration-core | >= 5.3.0, < 5.3.2 | 5.3.2 |
| Maven | org.springframework.integration:spring-integration-core | >= 5.1.0, < 5.1.12 | 5.1.12 |
| Maven | org.springframework.integration:spring-integration-core | >= 5.2.0, < 5.2.8 | 5.2.8 |
Details
As written in the advisory (Markdown source, shown as plain text).
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
External links from the advisory. They lead to third-party sites.
- https://nvd.nist.gov/vuln/detail/CVE-2020-5413
- https://github.com/spring-projects/spring-integration/commit/6a02b5abe97fabab6003d51b98dd45ab009a6e05
- https://github.com/spring-projects/spring-integration
- 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