RabbitMQ rabbitmq-server
RabbitMQ: Plaintext username:password stored in an insecure cookie after successful POST /login
RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.8 and 4.3.2, a successful POST /login caused is_authorized/2 to set an auth cookie containing base64-encoded username:password credentials without HttpOnly, Secure, SameSite, or expiration protections. Because base64 is encoding rather than encryption, an attacker with same-origin cross-site scripting, an HTTP-readable network position, or local access to the browser cookie store could recover the actual login credentials; older browsers that treated an absent SameSite attribute as None also sent the cookie cross-site. This issue is fixed in versions 4.2.8 and 4.3.2.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 4.2.0, < 4.2.8
- >= 4.3.0, < 4.3.2
Fixed in 4.2.8, 4.3.2
Mitigation
Upgrade rabbitmq-server to 4.2.8 or 4.3.2 or later.
References
- Vendor advisory github.com/rabbitmq/rabbitmq-server/security/a…
- Patch github.com/rabbitmq/rabbitmq-server/commit/df9…
- Patch github.com/rabbitmq/rabbitmq-server/commit/edf…
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.