Vulnerabilities · 2022 · Squid-cache
CVE-2022-41317
Squid-cache Squid vulnerability
An issue was discovered in Squid 4.9 through 4.17 and 5.0.6 through 5.6. Due to inconsistent handling of internal URIs, there can be Exposure of Sensitive Information about clients using the proxy via an HTTPS request to an internal cache manager URL. This is fixed in 5.7.
Affected products
Squid. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Squid-cache Squid runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- www.squid-cache.org/Versions/v4/changesets/SQUID-2022_1.patch · Patch
- www.squid-cache.org/Versions/v5/changesets/SQUID-2022_1.patch · Patch
- github.com/squid-cache/squid/security/advisories/GHSA-rcg9-7fqm-83mq · Mitigation
- www.openwall.com/lists/oss-security/2022/09/23/1 · Mitigation
- nvd.nist.gov/vuln/detail/CVE-2022-41317
- cve.org/CVERecord?id=CVE-2022-41317
More vulnerabilities in Squid-cache products
CVE-2025-62168CVE-2025-59362CVE-2025-54574CVE-2024-45802CVE-2024-37894CVE-2024-25617CVE-2024-25111CVE-2024-23638All 106
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.