CyberRota Analysis
AI-GeneratedRabbitMQ versions 3.13.0 to 3.13.18, 4.0.23, 4.1.14, 4.2.9, and 4.3.3 are vulnerable due to a flaw in handling proxy-derived client addresses, which may allow authenticated attackers to bypass source-address restrictions for loopback-restricted accounts. This vulnerability does not affect password authentication but could lead to unauthorized access if exploited. Organizations using affected RabbitMQ versions, particularly those relying on MQTT and MQTT over WebSocket behind a trusted proxy, should prioritize upgrading to the patched versions to mitigate this 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. From 3.13.0 until 3.13.18, 4.0.23, 4.1.14, 4.2.9, and 4.3.3, native MQTT and MQTT over WebSocket behind a trusted PROXY Protocol frontend could lose the proxy-derived client address before the MQTT authentication path checked loopback_users, causing the frontend-to-broker address to be treated as loopback. An attacker who can reach the trusted frontend and has valid credentials for a loopback-restricted account can therefore bypass the source-address restriction; the issue does not bypass password authentication. This issue is fixed in versions 3.13.18, 4.0.23, 4.1.14, 4.2.9, and 4.3.3.
Related CVEs
Other vulnerabilities affecting the same vendor(s)