Kryo Configuration Allows Code Execution with Unknown "Serialization Gadgets"
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 4%. Fixed in v4.3.23.RELEASE, v5.1.12.RELEASE, v5.2.8.RELEASE and 1 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Spring by VMware | >=4.3 <v4.3.23.RELEASE, >=5.1 <v5.1.12.RELEASE, >=5.2 <v5.2.8.RELEASE, >=5.3 <v5.3.2.RELEASE | v4.3.23.RELEASE, v5.1.12.RELEASE, v5.2.8.RELEASE, v5.3.2.RELEASE |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket