RabbitMQ rabbitmq-server
RabbitMQ: Consecutive topic wildcards cause combinatorial routing work
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.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.1high · scored by CNA · CWE-407
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
rabbitmq rabbitmq-server
- < 4.3.5
Fixed in 4.3.5
Mitigation
Upgrade rabbitmq-server to 4.3.5 or later.
References
- Vendor advisory github.com/rabbitmq/rabbitmq-server/security/a…
- Patch github.com/rabbitmq/rabbitmq-server/commit/c5e…
- Release notes github.com/rabbitmq/rabbitmq-server/releases/t…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.