RabbitMQ rabbitmq-server
RabbitMQ: Federation upstream skips vhost authorization allowing cross-vhost message access
RabbitMQ is a messaging and streaming broker. From 3.13.0 until 4.3.3, 4.2.9 , 4.1.14, 4.0.24, and 3.13.18, Federation upstream in RabbitMQ skips vhost authorization allowing cross-vhost message access. what the bug lets you do. A policymaker on one vhost reads and drains messages out of another vhost it has no permission on. With the default ack-mode the source messages are consumed (deleted), not copied. Why that should not 1. Federation validates the upstream URI without any vhost-access Cross-vhost message read/drain from a per-vhost policymaker, breaking vhost tenancy This issue is fixed in versions 4.3.3, 4.2.9 , 4.1.14, 4.0.24, and 3.13.18.
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.14
- >= 4.0.0, < 4.0.24
- >= 3.13.0, < 3.13.18
Fixed in 4.3.3, 4.2.9, 4.1.14, 4.0.24, 3.13.18
Mitigation
Upgrade rabbitmq-server to 4.3.3 or 4.2.9 or 4.1.14 or 4.0.24 or 3.13.18 or later.
References
- Vendor advisory github.com/rabbitmq/rabbitmq-server/security/a…
- 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.