RabbitMQ rabbitmq-server
RabbitMQ: CORS * reflects Origin with Allow-Credentials
RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.17, 4.0.22, 4.1.13, and 4.2.6, match_origin/1 returned the bare reflected Origin and allowed credentials even when the wildcard "" was configured, so the response echoed the attacker's origin together with Access-Control-Allow-Credentials. The affected code is rabbit_mgmt_cors.erl. When the management plugin is configured with a wildcard CORS origin (cors_allow_origins = ""), the handler reflects the request Origin back in Access-Control-Allow-Origin and also sends Access-Control-Allow-Credentials: true. A malicious web page that a signed-in administrator visits can then use that administrator's cached HTTP Basic credentials to issue authenticated, state-changing requests to the management API. Preconditions include The management plugin is configured with the wildcard cors_allow_origins = "*", which is an explicit operator misconfiguration A target administrator has a cached HTTP Basic-auth session in the browser. This issue is fixed in versions 3.13.17, 4.0.22, 4.1.13, and 4.2.6.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 3.13.0, < 3.13.17
- >= 4.0.0, < 4.0.22
- >= 4.1.0, < 4.1.13
- >= 4.2.0, < 4.2.6
Fixed in 3.13.17, 4.0.22, 4.1.13, 4.2.6
Mitigation
Upgrade rabbitmq-server to 3.13.17 or 4.0.22 or 4.1.13 or 4.2.6 or later.
References
- Vendor advisory github.com/rabbitmq/rabbitmq-server/security/a…
- 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.