Code execution in Spring Integration
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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2020-5413US | critical9.8 | — | ||
Spring Integration framework provides Kryo Codec implementations as an alternative for Java (de)serialization. When Kryo is configured with default options, all unregistered classe… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/spring-projects/spring-integrationPACKAGE
- https://github.com/spring-projects/spring-integration/commit/6a02b5abe97fabab6003d51b98dd45ab009a6e05WEB
- https://nvd.nist.gov/vuln/detail/CVE-2020-5413ADVISORY
- https://tanzu.vmware.com/security/cve-2020-5413WEB
- https://www.oracle.com//security-alerts/cpujul2021.htmlWEB
- https://www.oracle.com/security-alerts/cpuApr2021.htmlWEB
- https://www.oracle.com/security-alerts/cpuapr2022.htmlWEB
- https://www.oracle.com/security-alerts/cpuoct2021.htmlWEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan