CVE-2022-41317
First published: Sun Dec 25 2022(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Squid-Cache Squid | >=4.9<=4.17 | |
| Squid-Cache Squid | >=5.0.6<5.7 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
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.
- collector/nvd-index
- agent/weakness
- vendor/squid-cache
- canonical/squid-cache squid
- version/squid-cache squid/4.9
- version/squid-cache squid/4.17
- version/squid-cache squid/5.0.6