Data alteration and service disruption via unrestricted deserialization
Published Oct 19, 2023 · Updated Sep 12, 2024
Untrusted deserialization in Spring AMQP 1.0.0 through 2.4.16 and 3.0.0 through 3.0.9 allows remote authenticated users to disrupt service. SimpleMessageConverter and SerializerMessageConverter accept serialized message bodies for any class when no allowed-list pattern is configured. Reachability requires permission to publish malicious content to the RabbitMQ broker, and the published impact is limited to data alteration and service disruption.
Summary
What happened
Untrusted deserialization in Spring AMQP 1.0.0 through 2.4.16 and 3.0.0 through 3.0.9 allows remote authenticated users to disrupt service. SimpleMessageConverter and SerializerMessageConverter accept serialized message bodies for any class when no allowed-list pattern is configured. Reachability requires permission to publish malicious content to the RabbitMQ broker, and the published impact is limited to data alteration and service disruption.
The record
- CVE
- CVE-2023-34050
- Published
- Oct 19, 2023
- Updated
- Sep 12, 2024
- Vendor
- Spring
- Product
- Spring AMQP
- Classifications
- CWE-502, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 19, 2023CVE publishedPublication date reported by the CVE source.
- Sep 12, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0 <2.4.17
- Affected versionversion=3.0.0 <3.0.10
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo