RabbitMQ: Monitoring-tag user can restart federation links
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.13.15, 4.0.20, 4.1.11, 4.2.6, 4.3.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1, is_authorized/2 for the /federation-links/.../restart route uses is_authorized_monitor (accepts the monitoring tag), while allowed_methods permits DELETE and delete_resource/2 triggers rabbit_federation_link_sup:restart. There is no per-method elevation check and no comment marking it intentional. A read-only monitoring user can restart any federation link , a state-changing operation that disrupts message flow. Preconditions include rabbitmq_federation + rabbitmq_federation_management plugins enabled Attacker has credentials with the monitoring tag. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- rabbitmq rabbitmq-server
From 3.13.0 · fixed in 3.13.15; From 4.0.0 · fixed in 4.0.20; From 4.1.0 · fixed in 4.1.11; From 4.2.0 · fixed in 4.2.6; From 4.3.0 · fixed in 4.3.1
- rabbitmqBitnami
From 3.13.0 · fixed in 3.13.15; From 4.0.0 · fixed in 4.0.20; From 4.1.0 · fixed in 4.1.11; From 4.2.0 · fixed in 4.2.6; From 4.3.0 · fixed in 4.3.1