RabbitMQ rabbitmq-server
RabbitMQ: Stream Management Super-Stream Binding Keys Allocation Allows Low-Privilege Node Denial of Service
RabbitMQ is a messaging and streaming broker. From 4.1.0 until 4.3.3, 4.2.9, and 4.1.11, Stream Management Super-Stream Binding Keys Allocation Allows Low-Privilege Node Denial of Service. rabbitMQ 4.3.1 with rabbitmqstreammanagement enabled accepts PUT /api/stream/super-streams/{vhost}/{name} requests from an authenticated management user that can access the target vhost. When the request body contains the binding-keys field, the handler parses the attacker-controlled comma-separated string and builds the full stream-name list before checking whether the user has permission to configure the resulting streams. A low-privileged management user with vhost access but no configure, write, or read permission can therefore force large transient allocations before the resource permission check. In a 768 MB memory-limited container, one HTTP PUT with about 4.5 MB of JSON body killed the RabbitMQ container with Docker state exited true An authenticated low-privileged management user can kill a memory-limited RabbitMQ node with one HTTP This issue is fixed in versions 4.3.3, 4.2.9, and 4.1.11.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 4.3.0, < 4.3.3
- >= 4.2.0, < 4.2.9
- >= 4.1.0, < 4.1.11
Fixed in 4.3.3, 4.2.9, 4.1.11
Mitigation
Upgrade rabbitmq-server to 4.3.3 or 4.2.9 or 4.1.11 or later.
References
- Vendor advisory github.com/rabbitmq/rabbitmq-server/security/a…
- Patch github.com/rabbitmq/rabbitmq-server/commit/0f3…
- Patch github.com/rabbitmq/rabbitmq-server/commit/eb1…
2 more
- Release notes github.com/rabbitmq/rabbitmq-server/releases/t…
- 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.