How severe is CVE-2005-2917?

CVE-2005-2917 has a CVSS 2.0 base score of 5.0, rated medium severity.

Is CVE-2005-2917 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (87th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2005-2917?

CVE-2005-2917 primarily affects Squid. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2005-2917?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2005-2917 published?

CVE-2005-2917 was published on 2005-09-30 and last updated on 2026-06-16.

CVE-2005-2917

CVE-2005-2917 is a medium-severity vulnerability in Squid with a CVSS 2.0 base score of 5.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 2.0 base score 5.0)
EPSS exploit prediction: 3% (87th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Squid
Published: 2005-09-30
Last modified: 2026-06-16

Description

Squid 2.5.STABLE10 and earlier, while performing NTLM authentication, does not properly handle certain request sequences, which allows attackers to cause a denial of service (daemon restart).

Frequently asked questions

What is CVE-2005-2917?: Squid 2.5.STABLE10 and earlier, while performing NTLM authentication, does not properly handle certain request sequences, which allows attackers to cause a denial of service (daemon restart).
How severe is CVE-2005-2917?: CVE-2005-2917 has a CVSS 2.0 base score of 5.0, rated medium severity.
Is CVE-2005-2917 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (87th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2005-2917?: CVE-2005-2917 primarily affects Squid. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2005-2917?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2005-2917 published?: CVE-2005-2917 was published on 2005-09-30 and last updated on 2026-06-16.

References

Affected products (2)

cpe:2.3:a:squid:squid:*:*:*:*:*:*:*:*
cpe:2.3:a:squid:squid:2.5.9:*:*:*:*:*:*:*

More vulnerabilities in Squid

CVE-2005-0194 — Critical (CVSS 10.0): Squid 2.5, when processing the configuration file, parses empty Access Control Lists (ACLs), including proxy_auth ACLs…
CVE-2005-1711 — High (CVSS 7.5): Gibraltar Firewall 2.2 and earlier, when using the ClamAV update to 0.81 for Squid, uses a defunct ClamAV method to…
CVE-2005-1345 — High (CVSS 7.5): Squid 2.5.STABLE9 and earlier does not trigger a fatal error when it identifies missing or invalid ACLs in the…
CVE-2005-0173 — High (CVSS 7.5): squid_ldap_auth in Squid 2.5 and earlier allows remote authenticated users to bypass username-based Access Control…
CVE-2004-0189 — High (CVSS 7.5): The "%xx" URL decoding function in Squid 2.5STABLE4 and earlier allows remote attackers to bypass url_regex ACLs via a…
CVE-2002-0713 — High (CVSS 7.5): Buffer overflows in Squid before 2.4.STABLE6 allow remote attackers to cause a denial of service (crash) and possibly…

All CVEs affecting Squid →