Spring Security Advisory
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
- the SimpleMessageConverter or SerializerMessageConverter is used
- the user does not configure allowed list patterns
- untrusted message originators gain permissions to write messages to the RabbitMQ broker to send malicious content