Node termination via unbounded HTTP request bodies
Published Oct 24, 2023 · Updated Feb 13, 2025
Resource exhaustion in RabbitMQ Server 3.11.0 through 3.11.23 and 3.12.0 through 3.12.6 allows remote authenticated users to terminate a node. The management HTTP API accepts a message-publish request body without enforcing a size limit, allowing oversized message data to exhaust node memory. Exploitation requires an authenticated account with sufficient publishing rights, and the resulting exhaustion causes an out-of-memory-killer-like node termination.
Summary
What happened
Resource exhaustion in RabbitMQ Server 3.11.0 through 3.11.23 and 3.12.0 through 3.12.6 allows remote authenticated users to terminate a node. The management HTTP API accepts a message-publish request body without enforcing a size limit, allowing oversized message data to exhaust node memory. Exploitation requires an authenticated account with sufficient publishing rights, and the resulting exhaustion causes an out-of-memory-killer-like node termination.
The record
- CVE
- CVE-2023-46118
- Published
- Oct 24, 2023
- Updated
- Feb 13, 2025
- Vendor
- RabbitMQ
- Product
- RabbitMQ Server
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 24, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record 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=< 3.11.24
- Affected versionversion=< 3.12.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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