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.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
None
No additional conditions
Privileges Required
Low
Basic privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
None
No data leak
Integrity
None
No data modification
Availability
High
Complete denial of service
CVSS Vector v4.0
Weakness Type (CWE)
References 3
https://github.com/rabbitmq/rabbitmq-server/commit/c5ed7c4e97e02be688730803604c…
security-advisories@github.com
https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.5
security-advisories@github.com
https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-h964-v5mf-…
security-advisories@github.com