Get ahead
VMware offers training and certification to turbo-charge your progress.
Learn moreSpring Integration Redis queue endpoints use unrestricted Java deserialization by default. RedisQueueMessageDrivenEndpoint and RedisQueueInboundGateway deserialize data read from Redis lists, while RedisQueueOutboundGateway deserializes replies, using JdkSerializationRedisSerializer unless an application configures another serializer.
An attacker who can write crafted serialized data to a Redis list consumed by one of these endpoints can trigger deserialization of arbitrary classes. If a suitable gadget chain is present on the application's classpath, this can lead to remote code execution in the application process.
Applications are affected when they use one of these Redis queue endpoints with its default serializer and allow an untrusted or compromised client to write to the relevant Redis list.
Spring Integration:
| Fix version | Availability |
|---|---|
| 7.1.3 | OSS |
| 7.1.2.1 | Enterprise Support Only |
| 7.0.8 | OSS |
| 7.0.7.1 | Enterprise Support Only |
| 6.5.12 | Enterprise Support Only |
| 6.4.14 | Enterprise Support Only |
| 5.5.23 | Enterprise Support Only |
Applications that cannot upgrade should configure the affected Redis queue endpoints with a non-JDK serializer, such as a String or JSON serializer, and restrict write access to the consumed Redis lists to trusted producers.
This vulnerability was discovered and responsibly reported by Yu Bao from PayPal Cyber Security Team.
To report a security vulnerability for a project within the Spring portfolio, see the Security Policy