RabbitMQ: Web MQTT with PROXY Protocol enabled: a loopback-only user permission bypass
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| rabbitmq | >=3.13.0 <3.13.18, >=4.0.0 <4.0.23, >=4.1.0 <4.1.14, >=4.2.0 <4.2.9, >=4.3.0 <4.3.3 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket