| Reporter | Title | Published | Views | Family All 192 |
|---|---|---|---|---|
| Exploit for Server-generated Error Message Containing Sensitive Information in Squid-Cache Squid | 2 Nov 202509:42 | – | githubexploit | |
| Amazon Linux 2023 : squid (ALAS2023-2025-1238) | 28 Oct 202500:00 | – | nessus | |
| Amazon Linux 2 : squid, --advisory ALAS2-2025-3045 (ALAS-2025-3045) | 28 Oct 202500:00 | – | nessus | |
| Alibaba Cloud Linux 3 : 0170: squid:4 (ALINUX3-SA-2025:0170) | 17 Nov 202500:00 | – | nessus | |
| AlmaLinux 8 : squid:4 (ALSA-2025:19107) | 28 Oct 202500:00 | – | nessus | |
| AlmaLinux 9 : squid (ALSA-2025:20935) | 19 Nov 202500:00 | – | nessus | |
| AlmaLinux 10 : squid (ALSA-2025:21002) | 25 Nov 202500:00 | – | nessus | |
| Debian dla-4369 : squid - security update | 11 Nov 202500:00 | – | nessus | |
| Debian dsa-6047 : squid - security update | 30 Oct 202500:00 | – | nessus | |
| Fedora 41 : squid (2025-252c9276b3) | 27 Oct 202500:00 | – | nessus |
id: CVE-2025-62168
info:
name: Squid Proxy - HTTP Authentication Credentials Disclosure
author: xtr0nix
severity: critical
description: |
Squid versions prior to 7.2 fail to redact HTTP authentication credentials in error page responses. The Authorization header value is embedded in plain text inside the mailto: diagnostic block when Squid generates an error page (e.g. ERR_DNS_FAIL).
impact: |
Attackers can extract tokens and credentials used by trusted clients or backend applications proxied through Squid.
remediation: |
Update to the version 7.2+ or disable debug information in administrator mailto links generated by Squid by configuring squid.conf with email_err_data off.
reference:
- https://nvd.nist.gov/vuln/detail/CVE-2025-62168
- https://github.com/squid-cache/squid/security/advisories/GHSA-c8cc-phh7-xmxr
classification:
cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
cvss-score: 10.0
cve-id: CVE-2025-62168
epss-score: 0.6332
epss-percentile: 0.99108
cwe-id: CWE-209
metadata:
verified: true
max-request: 1
tags: cve,cve2025,info-disclosure,squid,proxy
variables:
token: "{{randstr}}"
invalid_host: "{{rand_base(16)}}.invalid"
http:
- raw:
- |+
GET http://{{invalid_host}}/ HTTP/1.1
Host: {{invalid_host}}
Authorization: Bearer {{token}}
unsafe: true
matchers:
- type: dsl
dsl:
- 'status_code == 503'
- 'contains(body, "mailto:")'
- 'contains(body, "ERR_DNS_FAIL")'
- 'contains(body, "{{token}}")'
condition: and
extractors:
- type: regex
part: body
name: leaked-token
regex:
- "Authorization%3A%20Bearer%20([^%]+)"
# digest: 4a0a00473045022100f4e50b1a31c0f595ef4d0a5c0c74ce0fefe8de23eef58d878c0a95bf68b802740220061a2e7ff3ce9a279a8e0412c1de93d27164735ad70120d6584012c6cf96fa6b:922c64590222798bb761d5b6d8e72950Data
Build on a solid foundation with Vulners data
We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data
Api
Power your application with Vulners API
The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access
App
Assess and manage vulnerabilities with Vulners tools
Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation