Code execution in Spring Integration
Critical severity
GitHub Reviewed
Published
Aug 5, 2020
to the GitHub Advisory Database
•
Updated Feb 1, 2023
Package
Affected versions
>= 4.3.0, < 4.3.23
>= 5.3.0, < 5.3.2
>= 5.1.0, < 5.1.12
>= 5.2.0, < 5.2.8
Patched versions
4.3.23
5.3.2
5.1.12
5.2.8
Description
Published by the National Vulnerability Database
Jul 31, 2020
Reviewed
Aug 3, 2020
Published to the GitHub Advisory Database
Aug 5, 2020
Last updated
Feb 1, 2023
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