CyberRota Analysis
AI-GeneratedAn authenticated user in RabbitMQ versions prior to 4.3.5 can exploit a flaw in the topic exchange binding mechanism to create excessive CPU and memory load, potentially disrupting message routing for all tenants. This vulnerability poses a high risk to environments utilizing RabbitMQ for messaging and streaming, particularly those with multi-tenant architectures. Organizations using affected versions should prioritize upgrading to 4.3.5 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. Prior to 4.3.5, an authenticated user who can bind a queue to a topic exchange and publish to it can use consecutive # segments in a binding key to make both topic matchers revisit the same trie-node and routing-key-suffix states without memoization. The matcher materializes duplicate destinations before deduplication, causing combinatorial CPU work and memory pressure that can disrupt routing for all tenants. This vulnerability is fixed in 4.3.5.