How severe is CVE-2004-2654?

CVE-2004-2654 has a CVSS 2.0 base score of 5.0, rated medium severity.

Is CVE-2004-2654 being actively exploited?

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

What products are affected by CVE-2004-2654?

CVE-2004-2654 affects Squid. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2004-2654?

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

When was CVE-2004-2654 published?

CVE-2004-2654 was published on 2004-12-31 and last updated on 2026-06-16.

CVE-2004-2654

CVE-2004-2654 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: 2% (78th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Squid
Published: 2004-12-31
Last modified: 2026-06-16

Description

The clientAbortBody function in client_side.c in Squid Web Proxy Cache before 2.6 STABLE6 allows remote attackers to cause a denial of service (segmentation fault) via unspecified vectors that trigger a null dereference. NOTE: in a followup advisory, a researcher claimed that the issue was a buffer overflow that was not fixed in STABLE6. However, the vendor's bug report clearly shows that the researcher later retracted this claim, because the tested product was actually STABLE5.

Frequently asked questions

What is CVE-2004-2654?: The clientAbortBody function in client_side.c in Squid Web Proxy Cache before 2.6 STABLE6 allows remote attackers to cause a denial of service (segmentation fault) via unspecified vectors that trigger a null dereference. NOTE: in a followup advisory, a researcher claimed that the issue was a buffer overflow that was not fixed in STABLE6. However, the vendor's bug report clearly shows that the researcher later retracted this claim, because the tested product was actually STABLE5.
How severe is CVE-2004-2654?: CVE-2004-2654 has a CVSS 2.0 base score of 5.0, rated medium severity.
Is CVE-2004-2654 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (78th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2004-2654?: CVE-2004-2654 affects Squid. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2004-2654?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2004-2654 published?: CVE-2004-2654 was published on 2004-12-31 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:squid:squid:2.5_stable5:*:*:*:*:*:*:*

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 →