Deserialization in Spring Amqp
CVE-2023-34050
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
Vulnerability class: Insecure Deserialization
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.0 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:H.
EPSS exploit prediction
EPSS 0.018, 79.3th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Spring Amqp — versions 1.0.0, 3.0.0
- VMware Spring Advanced Message Queuing Protocol
Weakness classification (CWE)
Public exploits and proof-of-concept code
1 public repository with exploit or proof-of-concept code for this CVE:
- X1r0z/spring-amqp-deserialization (13 stars, last pushed 2024-01-29): PoC of Spring AMQP Deserialization Vulnerability (CVE-2023-34050)
Also mentioned in 3 other repositories (cuijiung/temp, nomi-sec/PoC-in-GitHub, p4d0rn/Java_Zoo). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- spring.io/security/cve-2023-34050 (Mitigation, Vendor Advisory)
This CVE has public exploit evidence. See the latest CVEs with public exploits.