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
Metrics
Affected Vendors & Products
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: vmware
Published:
Updated: 2024-09-12T17:58:46.718Z
Reserved: 2023-05-25T17:21:56.203Z
Link: CVE-2023-34050
Updated: 2024-08-02T16:01:52.410Z
Status : Modified
Published: 2023-10-19T08:15:08.357
Modified: 2024-11-21T08:06:28.600
Link: CVE-2023-34050
OpenCVE Enrichment
No data.
Weaknesses