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.015 (73.6th percentile), scored .
Low probability of exploitation in the next 30 days, but still tracked. 74th percentile — 73.6% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.015 · newest: 0.015 · change: -0.000
Affected products
- Spring Amqp — versions 1.0.0, 3.0.0
- VMware Spring Advanced Message Queuing Protocol
Weakness classification (CWE)
Public proof-of-concept exploits
References
- spring.io/security/cve-2023-34050 (Mitigation, Vendor Advisory)
Frequently asked questions
- What is CVE-2023-34050?
- CVE-2023-34050 is a medium-severity vulnerability in Spring Amqp, classified under Deserialization of Untrusted Data. CVSS score: 5.0/10. Published 2023-10-19.
- How severe is CVE-2023-34050?
- Medium severity. CVSS v3 base score is 5.0 out of 10.
- Is CVE-2023-34050 known to be exploited?
- 4 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.