CVE Vulnerabilities

CVE-2025-62168

Generation of Error Message Containing Sensitive Information

Published: Oct 17, 2025 | Modified: Nov 05, 2025
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS 2.x
RedHat/V2
RedHat/V3
8.6 IMPORTANT
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

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.

Weakness

The product generates an error message that includes sensitive information about its environment, users, or associated data.

Affected Software

NameVendorStart VersionEnd Version
SquidSquid-cache*7.2 (excluding)
Red Hat Enterprise Linux 10RedHatsquid-7:6.10-6.el10_1.1*
Red Hat Enterprise Linux 10.0 Extended Update SupportRedHatsquid-7:6.10-5.el10_0.1*
Red Hat Enterprise Linux 7 Extended Lifecycle SupportRedHatsquid-7:3.5.20-17.el7_9.15*
Red Hat Enterprise Linux 8RedHatsquid:4-8100020251023131551.489197e6*
Red Hat Enterprise Linux 8.2 Advanced Update SupportRedHatsquid:4-8020020251028004321.4cda2c84*
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update SupportRedHatsquid:4-8040020251024000101.522a0ee4*
Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-OnRedHatsquid:4-8040020251024000101.522a0ee4*
Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update SupportRedHatsquid:4-8060020251027230224.ad008a3a*
Red Hat Enterprise Linux 8.6 Telecommunications Update ServiceRedHatsquid:4-8060020251027230224.ad008a3a*
Red Hat Enterprise Linux 8.6 Update Services for SAP SolutionsRedHatsquid:4-8060020251027230224.ad008a3a*
Red Hat Enterprise Linux 8.8 Telecommunications Update ServiceRedHatsquid:4-8080020251029094904.63b34585*
Red Hat Enterprise Linux 8.8 Update Services for SAP SolutionsRedHatsquid:4-8080020251029094904.63b34585*
Red Hat Enterprise Linux 9RedHatsquid-7:5.5-22.el9_7.1*
Red Hat Enterprise Linux 9.0 Update Services for SAP SolutionsRedHatsquid-7:5.2-1.el9_0.9*
Red Hat Enterprise Linux 9.2 Update Services for SAP SolutionsRedHatsquid-7:5.5-5.el9_2.10*
Red Hat Enterprise Linux 9.4 Extended Update SupportRedHatsquid-7:5.5-13.el9_4.4*
Red Hat Enterprise Linux 9.6 Extended Update SupportRedHatsquid-7:5.5-19.el9_6.2*
SquidUbuntudevel*
SquidUbuntuesm-infra/focal*
SquidUbuntujammy*
SquidUbuntunoble*
SquidUbuntuplucky*
SquidUbuntuquesting*
SquidUbuntuupstream*
Squid3Ubuntuesm-infra/bionic*
Squid3Ubuntuesm-infra/xenial*

Potential Mitigations

  • Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success.
  • If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files.
  • Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.

References