Information Exposure Affecting squid package, versions <7:4.15-10.module+el8.10.0+90691+00cd6d19.9


Severity

Recommended
0.0
high
0
10

Based on Oracle Linux security rating.

Threat Intelligence

Exploit Maturity
Proof of Concept
EPSS
63.32% (100th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ORACLE8-SQUID-13733771
  • published29 Oct 2025
  • disclosed17 Oct 2025

Introduced: 17 Oct 2025

CVE-2025-62168  (opens in a new tab)
CWE-209  (opens in a new tab)
CWE-550  (opens in a new tab)

How to fix?

Upgrade Oracle:8 squid to version 7:4.15-10.module+el8.10.0+90691+00cd6d19.9 or higher.
This issue was patched in ELSA-2025-19107.

NVD Description

Note: Versions mentioned in the description apply only to the upstream squid package and not the squid package as distributed by Oracle. See How to fix? for Oracle:8 relevant fixed versions and status.

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 Base Scores

version 3.1