نسخههای متأثر
- نسخههای متأثر
- <3.9.27-0ubuntu0.6
- نسخهٔ اصلاحشده
- 3.9.27-0ubuntu0.6
- نسخههای متأثر
- <3.12.1-1ubuntu1.7
- نسخهٔ اصلاحشده
- 3.12.1-1ubuntu1.7
- نسخههای متأثر
- <4.0.5-10ubuntu5.2
- نسخهٔ اصلاحشده
- 4.0.5-10ubuntu5.2
- نسخههای متأثر
- *
- نسخهٔ اصلاحشده
- اعلام نشده
- نسخههای متأثر
- <3.5.7-1ubuntu0.16.04.4+esm3
- نسخهٔ اصلاحشده
- 3.5.7-1ubuntu0.16.04.4+esm3
- نسخههای متأثر
- <3.6.10-1ubuntu0.5+esm1
- نسخهٔ اصلاحشده
- 3.6.10-1ubuntu0.5+esm1
- نسخههای متأثر
- <3.8.3-0ubuntu0.3+esm2
- نسخهٔ اصلاحشده
- 3.8.3-0ubuntu0.3+esm2
شرح آسیبپذیری
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.
پیوندها
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3
- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-xm9p-57xv-vxwc
- https://ubuntu.com/security/CVE-2026-67239
- https://ubuntu.com/security/notices/USN-8933-1
- https://www.cve.org/CVERecord?id=CVE-2026-67239

