CyberRota Analysis
AI-GeneratedRabbitMQ versions prior to 4.3.0, 4.2.6, 4.1.11, 4.0.20, and 3.13.15 are vulnerable due to improper validation of the content-header BodySize, allowing authenticated AMQP 0-9-1 clients with publish permissions to exploit this flaw. By manipulating the body size, an attacker can cause excessive memory consumption, leading to potential degradation of service across the cluster or complete memory exhaustion. Organizations using affected RabbitMQ versions, particularly those relying on AMQP 0-9-1 for messaging, should prioritize upgrading to the patched versions to mitigate this high-severity risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
RabbitMQ is a messaging and streaming broker. Prior to versions 4.3.0, 4.2.6, 4.1.11, 4.0.20, and 3.13.15, The content-header BodySize (a uint64) was stored without validation against max_message_size. The size check ran only when assembly completed. By declaring body_size = 2^63-1 and then streaming fragments, a client ensured that check_msg_size never fired, so the accumulated body size went unbounded. A reader process accumulates memory until the memory alarm fires, degrading all publishers cluster-wide, or until the node runs out of memory. The memory alarm provides only partial mitigation, since it is reactive rather than preventive. AMQP 0-9-1 is the most widely used protocol, and any publisher can trigger this condition. Preconditions include Any authenticated AMQP 0-9-1 client with publish permission can exploit this.. This issue is fixed in versions 4.3.0, 4.2.6, 4.1.11, 4.0.20, and 3.13.15.