First published: Thu Oct 19 2023(Updated: )
In spring AMQP versions 1.0.0 to 2.4.16 and 3.0.0 to 3.0.9 , 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, an 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
Credit: security@vmware.com security@vmware.com
Affected Software | Affected Version | How to fix |
---|---|---|
Vmware Spring Advanced Message Queuing Protocol | >=1.0.0<2.4.16 | |
Vmware Spring Advanced Message Queuing Protocol | >=3.0.0<3.0.9 | |
redhat/spring-amqp | <2.7.17 | 2.7.17 |
redhat/spring-amqp | <3.0.12 | 3.0.12 |
redhat/spring-amqp | <3.1.5 | 3.1.5 |
redhat/spring-amqp | <3.2.0 | 3.2.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-34050 is a vulnerability in Spring AMQP versions 1.0.0 to 2.4.16 and 3.0.0 to 3.0.9 that allows deserialization of data from untrusted sources.
CVE-2023-34050 affects VMware Spring Advanced Message Queuing Protocol versions 1.0.0 to 2.4.16 and 3.0.0 to 3.0.9.
The severity of CVE-2023-34050 is medium with a CVSS score of 5.
To fix CVE-2023-34050, upgrade to a patched version of Spring AMQP (2.4.17 or 3.0.10 or higher) or apply the recommended security patches.
More information about CVE-2023-34050 can be found at the following reference: [CVE-2023-34050](https://spring.io/security/cve-2023-34050).