نسخههای متأثر
- نسخههای متأثر
- <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.2.7 and 4.3.1, rabbit_pid_codec:decompose_from_binary/1 parses a caller-supplied ETF-encoded binary and calls binary_to_atom(Node, utf8) on the node-name field. It is reached from rabbit_volatile_queue:pid_from_name/2, which is invoked for any queue name / routing key beginning amq.rabbitmq.reply-to.. The CandidateNodes membership check happens after the atom is created, and the surrounding try/catch cannot reclaim atoms (they are never GC'd). binary_to_existing_atom is not used. Any authenticated AMQP client can crash the entire Erlang VM (all vhosts, all connections) with ~1M cheap requests. Preconditions include Authenticated AMQP 0-9-1 connection to any vhost No per-connection rate limit low enough to make ~1M operations infeasible. This issue is fixed in versions 4.2.7 and 4.3.1.
پیوندها
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.7
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.1
- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-x96j-244m-mrr2
- https://ubuntu.com/security/CVE-2026-67238
- https://ubuntu.com/security/notices/USN-8933-1
- https://www.cve.org/CVERecord?id=CVE-2026-67238

