CyberRota Analysis
AI-GeneratedRabbitMQ versions 4.2.0 to 4.2.8 and 4.3.2 are vulnerable due to improper handling of authentication mechanism cookies, which can result in non-ASCII cookie names that violate RFC 6265. While this vulnerability does not allow for direct code execution or data exfiltration, it may lead to stale authentication preferences persisting across user sessions. Organizations using affected versions should prioritize upgrading to 4.2.8 or 4.3.2 to mitigate potential authentication issues.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.8 and 4.3.2, get_auth_mechanism/1 used term_to_binary/1 on the strict_auth_mechanism or preferred_auth_mechanism atom when clearing the corresponding cookie, producing a non-ASCII cookie name that violates RFC 6265 and can prevent the browser from deleting the preference. The issue is not directly exploitable for code execution or data exfiltration; its security relevance is limited to stale authentication-mechanism preferences persisting across logout and login cycles. This issue is fixed in versions 4.2.8 and 4.3.2.