| Package | Affected versions | Patched versions |
|---|---|---|
| rabbitmq server | ≥ 3.13.0, < 3.13.18≥ 4.0.0, < 4.0.23≥ 4.1.0, < 4.1.14≥ 4.2.0, < 4.2.9≥ 4.3.0, < 4.3.3 | 3.13.184.0.234.1.144.2.94.3.3 |
RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.18 and 4.0.23 and 4.1.14 and 4.2.9 and 4.3.3, Stored XSS via TLS peer-certificate DN in stream-management UI (sibling of V-11). lines 102/106/110 render peercertsubject / peercertissuer with raw <%= %> and no fmtstring(). RFC4514 backslash-escaping of </> is HTML-inert and bypassable (<img ... //>). Requires non-default config: a stream TLS listener with verifypeer and an attacker-obtainable trusted cert with a malicious Same as the connection.ejs finding, against operators viewing the stream-connection detail rabbitmqstream + rabbitmqstreammanagement enabled with a TLS listener using verifypeer Attacker can obtain a certificate signed by a CA the listener trusts, with attacker-chosen DN An operator views the. This issue is fixed in versions 3.13.18 and 4.0.23 and 4.1.14 and 4.2.9 and 4.3.3.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free