Consumer crash via unbounded inbound message assembly
Published Oct 24, 2023 · Updated Sep 11, 2024
Uncontrolled resource consumption in RabbitMQ Java Client before 5.18.0 allows remote authenticated users to crash consumers via large messages. AMQCommand's CommandAssembler accepted body frames without enforcing a maximum aggregate body length, allowing the declared size to drive unbounded in-memory assembly. Remote authenticated users able to publish an oversized message through the broker can exhaust the receiving consumer's JVM heap and trigger an out-of-memory error.
Summary
What happened
Uncontrolled resource consumption in RabbitMQ Java Client before 5.18.0 allows remote authenticated users to crash consumers via large messages. AMQCommand's CommandAssembler accepted body frames without enforcing a maximum aggregate body length, allowing the declared size to drive unbounded in-memory assembly. Remote authenticated users able to publish an oversized message through the broker can exhaust the receiving consumer's JVM heap and trigger an out-of-memory error.
The record
- CVE
- CVE-2023-46120
- Published
- Oct 24, 2023
- Updated
- Sep 11, 2024
- Vendor
- RabbitMQ
- Product
- RabbitMQ Java Client
- Classifications
- CWE-400, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 24, 2023CVE publishedPublication date reported by the CVE source.
- Sep 11, 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=0 <5.18.0
- Affected versionversion=< 5.18.0
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.
Public exploit references
- Upstream oversized-message proof of conceptproof of concept · demonstrated
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