LiveActive security incident?Get immediate response
CVE Record

CVE-2009-2621: Squid 3.0 through 3.0.STABLE16 and 3.1 through 3.1.0.11 does not properly enforce "buffer limits and relate...

Squid 3.0 through 3.0.STABLE16 and 3.1 through 3.1.0.11 does not properly enforce "buffer limits and related bound checks," which allows remote attackers to cause a denial of service via (1) an incomplete request or (2) a request with a large header size, related to (a) HttpMsg.cc and (b) client_side.cc.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This flaw lets a remote sender crash or disrupt affected Squid proxy versions by sending malformed or oversized HTTP request data. The available sources describe denial of service, not data theft or code execution. Business urgency depends on whether legacy Squid 3.0 or early 3.1 proxies remain reachable by users or the internet. Exposure is most likely in legacy environments still running the listed Squid 3.0 or early 3.1 builds, especially forward or reverse proxies reachable by untrusted clients. Modern maintained Squid deployments are less likely affected, but the source bundle does not confirm every downstream package state. Prioritize remediation where Squid is internet-facing or supports critical business traffic. This is an availability risk rather than a confirmed breach vector. Legacy systems should be handled promptly because a simple remote disruption against a proxy can affect many downstream users and services. Mitigation focus: Identify and retire Squid versions listed as affected.; Apply Squid or operating-system vendor updates that include the referenced fix.; If updates are delayed, restrict proxy access to trusted networks only..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2009-2621 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.