Vulnerability record · CVE-2009-2622 · published 28 July 2009
CVE-2009-2622: Squid proxy input validation flaw allows remote denial of service
Squid Cache · Squid
Squid 3.0 through 3.0.STABLE16 and 3.1 through 3.1.0.11 fail to properly validate malformed HTTP requests and replies, including missing or mismatched protocol identifiers, missing or negative status values, missing versions, and missing or invalid status numbers. The flaw is in HttpMsg.cc and HttpReply.cc, and a remote attacker can crash or disrupt the proxy service.
Description
Squid 3.0 through 3.0.STABLE16 and 3.1 through 3.1.0.11 allows remote attackers to cause a denial of service via malformed requests including (1) "missing or mismatched protocol identifier," (2) missing or negative status value," (3) "missing version," or (4) "missing or invalid status number," related to (a) HttpMsg.cc and (b) HttpReply.cc.
AV:N/AC:L/Au:N/C:N/I:N/A:P
Automated analysis
medium priorityThe flaw is remotely reachable without authentication and has high EPSS, but it only causes denial of service with no confidentiality or integrity impact and a CVSS base score of 5.0.
What it is
Squid 3.0 through 3.0.STABLE16 and 3.1 through 3.1.0.11 fail to properly validate malformed HTTP requests and replies, including missing or mismatched protocol identifiers, missing or negative status values, missing versions, and missing or invalid status numbers. The flaw is in HttpMsg.cc and HttpReply.cc, and a remote attacker can crash or disrupt the proxy service.
Impact
An unauthenticated remote attacker can cause a denial of service against the Squid proxy, interrupting web access for all users relying on it. There is no confidentiality or integrity impact per the CVSS vector.
Attack surface
The flaw is reachable over the network via malformed HTTP requests or replies processed by Squid; the CVSS vector AV:N/AC:L/Au:N indicates no authentication and no user interaction are required.
Exploitation
Not listed in CISA KEV and no public exploit references are tagged in the record, but EPSS is 0.56908 (99th percentile), indicating a high predicted likelihood of exploitation activity.
What to do
- Apply the vendor patch referenced in the Squid advisory SQUID-2009_2 and changeset b9661, or upgrade to a fixed Squid release.
- Restrict network access to Squid proxy ports to trusted clients where feasible.
- Monitor vendor and distribution advisories (Mandriva MDVSA-2009:161 and MDVSA-2009:178) for packaged updates.
- If patching is delayed, consider rate limiting or filtering malformed HTTP traffic at the network edge.
Detection
- Monitor Squid logs for crashes, restarts, or abnormal termination correlated with malformed HTTP requests.
- Inspect proxy traffic for requests with missing or mismatched protocol identifiers, missing versions, or invalid status values.
- Alert on repeated malformed request patterns from a single source IP targeting the proxy.
- Track service availability of Squid instances for unexplained outages.
This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.
Affected products
1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
Track CVE-2009-2622 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2009-2622), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.