CVE-2022-41317: Medium severity 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 Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
alpine/squidto a version that resolves this vulnerability.Fixed in 5.7-r0 - Upgrade
Upgrade
debian/squidto a version that resolves this vulnerability.Fixed in 5.7-1 - Upgrade
Upgrade
debian/squidto a version that resolves this vulnerability.Fixed in 5.7-2+deb12u5Fixed in 5.7-2+deb12u6Fixed in 6.13-2+deb13u3Fixed in 6.13-2+deb13u4Fixed in 7.8-1 - Upgrade
Upgrade
Squidto a version that resolves this vulnerability.Fixed in 5.7
Event History
Frequently Asked Questions
What is the vulnerability ID for this issue in Squid?
The vulnerability ID for this issue in Squid is CVE-2022-41317.
What is the severity of CVE-2022-41317?
The severity of CVE-2022-41317 is medium with a CVSS score of 6.5.
What is the affected software for CVE-2022-41317?
The affected software for CVE-2022-41317 is Squid versions 4.9 through 4.17 and 5.0.6 through 5.6.
How can I fix CVE-2022-41317?
To fix CVE-2022-41317, update your Squid installation to version 5.7 or higher.
Where can I find more information about CVE-2022-41317?
You can find more information about CVE-2022-41317 on the Squid-cache website and the GitHub Security Advisory.