Kryo Configuration Allows Code Execution with Unknown "Serialization Gadgets"
Spring by VMware Spring Integration
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.integration:spring-integration-core Maven |
|
|
Spring by VMware Spring Integration
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.integration:spring-integration-core Maven |
|
|
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.
From the CVE record · pivotal
Spring Integration’s Kryo Codec resolves unregistered classes on demand when configured with default options. Deserializing attacker-provided data under those conditions can execute malicious code through deserialization gadgets. The input does not specify network or local access, authentication requirements, or user interaction.
Teams using Maven package org.springframework.integration:spring-integration-core in versions >=4.3.0 <4.3.23, >=5.1.0 <5.1.12, >=5.2.0 <5.2.8, or >=5.3.0 <5.3.2 should check their deployments.