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
References
Link | Resource |
---|---|
https://spring.io/security/cve-2023-34050 | Mitigation Vendor Advisory |
https://spring.io/security/cve-2023-34050 | Mitigation Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
21 Nov 2024, 08:06
Type | Values Removed | Values Added |
---|---|---|
CVSS |
v2 : v3 : |
v2 : unknown
v3 : 5.0 |
References | () https://spring.io/security/cve-2023-34050 - Mitigation, Vendor Advisory |
Information
Published : 2023-10-19 08:15
Updated : 2024-11-21 08:06
NVD link : CVE-2023-34050
Mitre link : CVE-2023-34050
CVE.ORG link : CVE-2023-34050
JSON object : View
Products Affected
vmware
- spring_advanced_message_queuing_protocol
CWE
CWE-502
Deserialization of Untrusted Data