نسخههای متأثر
- نسخههای متأثر
- <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 4.2.0 until 4.2.8 and 4.3.2, set_token_auth/2 inserted a bearer token from the Authorization header or access_token cookie into OAuth bootstrap JavaScript without escaping, allowing attacker-controlled token content to execute JavaScript in the management UI origin. The endpoint is exposed before authentication only when management.oauth_enabled is true, and exploitation through the cookie path additionally requires the attacker to plant an access_token cookie on the management host. This issue is fixed in versions 4.2.8 and 4.3.2.
پیوندها
- https://github.com/rabbitmq/rabbitmq-server/commit/5cd6d841d84450324a4613501ed917d98828af23
- https://github.com/rabbitmq/rabbitmq-server/commit/a8041d528c1a71af4cb75ade247ed082fe6b83fb
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.8
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.2
- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-2rf7-f6r6-8rwh
- https://ubuntu.com/security/CVE-2026-67237
- https://ubuntu.com/security/notices/USN-8933-1
- https://www.cve.org/CVERecord?id=CVE-2026-67237

