Description
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
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| Spring | Spring AMQP | 1.0.0 – < 2.4.17, 3.0.0 – < 3.0.10 | 2.4.17 |
Public exploits
Exploit or proof-of-concept code for this vulnerability is publicly available, which lowers the bar for attackers. Treat it as a reason to patch sooner.
GitHub 1 repository
-
X1r0z/spring-amqp-deserialization ★ 13 · Oct 20, 2023
PoC of Spring AMQP Deserialization Vulnerability (CVE-2023-34050)
Sources: PoC-in-GitHub, Metasploit Framework, Exploit-DB — updated daily. Only links are listed; no exploit code is hosted here.
Advisories 3
- NCSC-2024-0332 Kwetsbaarheden verholpen in Siemens producten NCSC-NL (Netherlands) · Aug 13, 2024
- ICSA-24-228-06 Siemens SINEC NMS CISA ICS & IT advisories · Aug 13, 2024
- SSA-784301 SSA-784301: Multiple Vulnerabilities in SINEC NMS Before V3.0 Siemens ProductCERT · Aug 13, 2024