نسخههای متأثر
- نسخههای متأثر
- <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. Prior to versions 4.3.0, 4.2.6, 4.1.11, 4.0.20, and 3.13.15, The content-header BodySize (a uint64) was stored without validation against max_message_size. The size check ran only when assembly completed. By declaring body_size = 2^63-1 and then streaming fragments, a client ensured that check_msg_size never fired, so the accumulated body size went unbounded. A reader process accumulates memory until the memory alarm fires, degrading all publishers cluster-wide, or until the node runs out of memory. The memory alarm provides only partial mitigation, since it is reactive rather than preventive. AMQP 0-9-1 is the most widely used protocol, and any publisher can trigger this condition. Preconditions include Any authenticated AMQP 0-9-1 client with publish permission can exploit this.. This issue is fixed in versions 4.3.0, 4.2.6, 4.1.11, 4.0.20, and 3.13.15.
پیوندها
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.0
- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-q8g2-pc7m-m3jw
- https://ubuntu.com/security/CVE-2026-67235
- https://ubuntu.com/security/notices/USN-8933-1
- https://www.cve.org/CVERecord?id=CVE-2026-67235

