RabbitMQ: Plaintext username:password stored in an insecure cookie after successful POST /login
rabbitmq-server
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| rabbitmq rabbitmq-server |
| No fix yet |
Original description
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.
From the CVE record · GitHub_M