rabbitmq-server: RabbitMQ: Federation upstream skips vhost authorization allowing cross-vhost message access
What fixes it
No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.
Description
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.
Text from CVE List
Affected versions 5
- rabbitmq-serveraffected: >= 4.3.0, < 4.3.3CVE List
- rabbitmq-serveraffected: >= 4.2.0, < 4.2.9CVE List
- rabbitmq-serveraffected: >= 4.1.0, < 4.1.14CVE List
- rabbitmq-serveraffected: >= 4.0.0, < 4.0.24CVE List
- rabbitmq-serveraffected: >= 3.13.0, < 3.13.18CVE List