همهٔ گزارش‌ها
متوسط

rabbitmq-server: rabbitmq-server: Access control bypass via PROXY protocol handling in MQTT

متن اصلی

نسخه‌های متأثر

نسخه‌های متأثر
نامشخص
نسخهٔ اصلاح‌شده
اعلام نشده
نسخه‌های متأثر
نامشخص
نسخهٔ اصلاح‌شده
اعلام نشده
نسخه‌های متأثر
نامشخص
نسخهٔ اصلاح‌شده
اعلام نشده
نسخه‌های متأثر
نامشخص
نسخهٔ اصلاح‌شده
اعلام نشده
نسخه‌های متأثر
نامشخص
نسخهٔ اصلاح‌شده
اعلام نشده

بهره‌برداری

CVE-2026-67411

احتمال بهره‌برداری در ۳۰ روز آینده: 0.32%

FIRST EPSS · ۱۴۰۵/۰۸/۲۸

شرح آسیب‌پذیری

RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.18, 4.0.23, 4.1.14, 4.2.9, and 4.3.3, native MQTT and MQTT over WebSocket behind a trusted PROXY Protocol frontend could lose the proxy-derived client address before the MQTT authentication path checked loopback_users, causing the frontend-to-broker address to be treated as loopback. An attacker who can reach the trusted frontend and has valid credentials for a loopback-restricted account can therefore bypass the source-address restriction; the issue does not bypass password authentication. This issue is fixed in versions 3.13.18, 4.0.23, 4.1.14, 4.2.9, and 4.3.3.

A flaw was found in rabbitmq-server. When native Message Queuing Telemetry Transport (MQTT) or MQTT over WebSockets operates behind a trusted proxy utilizing the PROXY protocol, the broker may drop the client IP address before enforcing user restriction checks. This failure causes external connections to be incorrectly identified as local loopback traffic. A remote attacker with valid credentials for an account restricted to local access can exploit this flaw to bypass source-address restrictions and connect remotely.