CVE-2025-62168: Squid vulnerable to information disclosure via authentication credential leakage in error handling
Squid is a caching proxy for the Web. In Squid versions prior to 7.2, a failure to redact HTTP authentication credentials in error handling allows information disclosure. The vulnerability allows a script to bypass browser security protections and learn the credentials a trusted client uses to authenticate. This potentially allows a remote client to identify security tokens or credentials used internally by a web application using Squid for backend load balancing. These attacks do not require Squid to be configured with HTTP authentication. The vulnerability is fixed in version 7.2. As a workaround, disable debug information in administrator mailto links generated by Squid by configuring squid.conf with emailerrdata off.
Other sources
Squid vulnerable to information disclosure via authentication credential leakage in error handling
— Microsoft
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-62168?
CVE-2025-62168 is classified as a security vulnerability that allows information disclosure due to improper handling of HTTP authentication credentials.
How do I fix CVE-2025-62168?
To mitigate CVE-2025-62168, upgrade to Squid version 7.2 or later, where the issue has been addressed.
What versions of Squid are affected by CVE-2025-62168?
CVE-2025-62168 affects all Squid versions prior to 7.2.
What is the impact of CVE-2025-62168 on user credentials?
CVE-2025-62168 allows scripts to bypass browser security protections and potentially access trusted client credentials.
Is there a workaround for CVE-2025-62168?
The recommended action for CVE-2025-62168 is to update to the latest version of Squid, as there are no effective workarounds to fully mitigate the vulnerability.