cve/2023/CVE-2023-34050.md

### [CVE-2023-34050](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-34050)
![](https://img.shields.io/static/v1?label=Product&message=Spring%20AMQP&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=1.0.0%3C%202.4.17%20&color=brighgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=n%2Fa&color=brighgreen)

### Description

In spring AMQP versions 1.0.0 to2.4.16 and 3.0.0 to 3.0.9 , allowed list patterns for deserializable classnames were added to Spring AMQP, allowing users to lock down deserialization ofdata in messages from untrusted sources; however by default, when no allowedlist was provided, all classes could be deserialized.Specifically, an application isvulnerable 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

### POC

#### Reference
No PoCs from references.

#### Github
- https://github.com/X1r0z/spring-amqp-deserialization
- https://github.com/nomi-sec/PoC-in-GitHub
- https://github.com/p4d0rn/Java_Zoo