CVE-2025-62168
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-10-17

Last updated on: 2025-11-05

Assigner: GitHub, Inc.

Description
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 email_err_data off.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-10-17
Last Modified
2025-11-05
Generated
2026-05-07
AI Q&A
2025-10-17
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
squid-cache squid to 7.2 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-209 The product generates an error message that includes sensitive information about its environment, users, or associated data.
CWE-550 Certain conditions, such as network failure, will cause a server error message to be displayed.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability in Squid versions prior to 7.2 involves a failure to redact HTTP authentication credentials in error handling. It allows a script to bypass browser security protections and obtain the credentials a trusted client uses to authenticate. This means an attacker can potentially learn sensitive authentication information that should be protected.


How can this vulnerability impact me? :

The vulnerability can lead to information disclosure where a remote client can identify security tokens or credentials used internally by a web application that uses Squid for backend load balancing. This can compromise the security of the application by exposing authentication credentials to unauthorized parties.


What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability immediately, upgrade Squid to version 7.2 or later. As a workaround, disable debug information in administrator mailto links generated by Squid by adding the configuration directive 'email_err_data off' to your squid.conf file.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart