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.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
High
Difficult to exploit
Attack Requirements
Present
Additional conditions required
Privileges Required
Low
Basic privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
None
No data modification
Availability
None
No disruption
CVSS Vector v4.0
Weakness Type (CWE)
Vulnerable Products
rabbitmq:rabbitmq-server
References 5
https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-4r6f-9cpw-…
https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-4r6f-9cpw-f6g6
https://github.com/rabbitmq/rabbitmq-server/commit/a7528314840c4f8dc9904684f9f9…
https://github.com/rabbitmq/rabbitmq-server/commit/a7528314840c4f8dc9904684f9f97ffa7aac6349
https://github.com/rabbitmq/rabbitmq-server/commit/edbead0eabbd65925d0dc914a22d…
https://github.com/rabbitmq/rabbitmq-server/commit/edbead0eabbd65925d0dc914a22d6a29e155e646
https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9
https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9
https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3
https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3