RabbitMQ rabbitmq-server
RabbitMQ: Web MQTT with PROXY Protocol enabled: a loopback-only user permission bypass
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 4.3.0, < 4.3.3
- >= 4.2.0, < 4.2.9
- >= 4.1.0, < 4.1.14
- >= 4.0.0, < 4.0.23
- >= 3.13.0, < 3.13.18
Fixed in 4.3.3, 4.2.9, 4.1.14, 4.0.23, 3.13.18
Mitigation
Upgrade rabbitmq-server to 4.3.3 or 4.2.9 or 4.1.14 or 4.0.23 or 3.13.18 or later.
References
- Vendor advisory github.com/rabbitmq/rabbitmq-server/security/a…
- Patch github.com/rabbitmq/rabbitmq-server/commit/a75…
- Patch github.com/rabbitmq/rabbitmq-server/commit/edb…
2 more
- Release notes github.com/rabbitmq/rabbitmq-server/releases/t…
- Release notes github.com/rabbitmq/rabbitmq-server/releases/t…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.