VMware offers training and certification to turbo-charge your progress.Learn more
In 2016, allowed list patterns for deserializable class names were added to Spring AMQP, allowing users to lock down deserialization of data in messages from untrusted sources; however by default, when no allowed list was provided, all classes could be deserialized.
Specifically, and application is vulnerable if
Spring Boot dependency management will pull in the corrected versions, starting with Boot versions 2.7.17, 3.0.12, 3.1.5, and 3.2.0.
Allowed class name patterns are now required.
However, users who wish to revert to the previous behavior of trusting all, can set a global environment property or system property; refer to the Java Deserialization documentation section
This vulnerability was responsibly reported by L0ne1y.