CVE-2022-41317

CVE-2022-41317 is a medium-severity vulnerability in Squid-cache Squid with a CVSS 3.x base score of 6.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-697.

Key facts

Description

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.

Frequently asked questions

What is CVE-2022-41317?
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.
How severe is CVE-2022-41317?
CVE-2022-41317 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2022-41317 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (74th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2022-41317?
CVE-2022-41317 affects Squid-cache Squid. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2022-41317?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2022-41317 published?
CVE-2022-41317 was published on 2022-12-25 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Squid-cache Squid

All CVEs affecting Squid-cache Squid →

Other CWE-697 vulnerabilities

Browse all CWE-697 vulnerabilities →

Threat intelligence

Threat-intel indicators referencing this CVE: