RabbitMQ: Stored HTML Injection in RabbitMQ Management OAuth Error Handling
- 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.19, 4.0.24, 4.1.15, 4.2.10, 4.3.5
- 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: poc
- Automatable: no
- Technical impact: partial
Summary
RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.19, 4.0.24, 4.1.15, 4.2.10, and 4.3.5, RabbitMQ Management rendered an AMQP authorization-error reason containing an attacker-controlled queue name as HTML when the OAuth management UI was enabled. Exploitation requires an attacker with queue configure permission, a management administrator who can see but cannot read that queue, and the administrator clicking Get Message(s). A queue name containing a base element can then retarget the automatic relative refresh because the Content Security Policy omits base-uri and connect-src, and an attacker endpoint that permits the management origin through CORS can receive the victim's Authorization header. This issue is fixed in versions 3.13.19, 4.0.24, 4.1.15, 4.2.10, and 4.3.5.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- rabbitmq rabbitmq-server
From 3.13.0 · fixed in 3.13.19; From 4.0.0 · fixed in 4.0.24; From 4.1.0 · fixed in 4.1.15; From 4.2.0 · fixed in 4.2.10; From 4.3.0 · fixed in 4.3.5
- rabbitmqBitnami
From 3.13.0 · fixed in 3.13.19; From 4.0.0 · fixed in 4.0.24; From 4.1.0 · fixed in 4.1.15; From 4.2.0 · fixed in 4.2.10; From 4.3.0 · fixed in 4.3.5