Skip to content
Fencer Vulns
medium 5.0

CVE-2005-2794 json

store.c in Squid 2.5.STABLE10 and earlier allows remote attackers to cause a denial of service (crash) via certain aborted requests that tr…

published 2005-09-07 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-2795

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.1%
EPSS 3.1% chance of exploitation in 30 days, percentile 88%
public exploits
0
none known

Summary

store.c in Squid 2.5.STABLE10 and earlier allows remote attackers to cause a denial of service (crash) via certain aborted requests that trigger an assert error related to STORE_PENDING.

Patch / fix

  • squid Debian 14, Debian 13, Debian 12 2.5.10-5

debian advisories DEBIAN-CVE-2005-2794

  • squid RHEL 3 7:2.5.STABLE3-6.3E.14
  • squid RHEL 4 7:2.5.STABLE6-3.4E.11

red hat advisories RHSA-2005:766

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2005-2794 updated

security flaw

  • Red Hat Desktop version 3 squid 2.5.STABLE3-6.3E.14 Red Hat Enterprise Linux AS version 3 squid 2.5.STABLE3-6.3E.14 Red Hat Enterprise Linux AS version 4 squid 2.5.STABLE6-3.4E.11 Red Hat Enterprise Linux Desktop version 4 squid 2.5.STABLE6-3.4E.11 Red Hat Enterprise Linux ES version 3 squid 2.5.STABLE3-6.3E.14 Red Hat Enterprise Linux ES version 4 squid 2.5.STABLE6-3.4E.11
    +2 more products
    Red Hat Enterprise Linux WS version 3 squid 2.5.STABLE3-6.3E.14 Red Hat Enterprise Linux WS version 4 squid 2.5.STABLE6-3.4E.11
    fixed: vendor fix RHSA-2005:766

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.15% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.