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.
History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: pivotal

Published: 2020-07-31T19:40:19.970815Z

Updated: 2024-09-16T16:22:53.854Z

Reserved: 2020-01-03T00:00:00

Link: CVE-2020-5413

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2020-07-31T20:15:13.017

Modified: 2024-11-21T05:34:07.263

Link: CVE-2020-5413

cve-icon Redhat

No data.