LiveActive security incident?Get immediate response
CVE Record

CVE-2012-2213: Squid 3.1.9 allows remote attackers to bypass the access configuration for the CONNECT method by providing...

Squid 3.1.9 allows remote attackers to bypass the access configuration for the CONNECT method by providing an arbitrary allowed hostname in the Host HTTP header. NOTE: this issue might not be reproducible, because the researcher is unable to provide a squid.conf file for a vulnerable system, and the observed behavior is consistent with a squid.conf file that was (perhaps inadvertently) designed to allow access based on a "req_header Host" acl regex that matches www.uol.com.br

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This CVE describes a possible Squid proxy filtering bypass. A remote user may have been able to access blocked CONNECT destinations by putting an allowed hostname in the HTTP Host header. The public record also warns the issue may not be reproducible and may reflect a permissive squid.conf rule instead of a Squid flaw. Exposure appears limited to Squid 3.1.9 forward-proxy deployments using CONNECT filtering and Host-header-based ACLs. The source bundle does not identify broader affected versions, CPEs, a confirmed vulnerable configuration, or a vendor patch. Prioritize review if Squid enforces outbound web access policy, regulatory egress controls, or segmentation. Otherwise, urgency is moderate-to-low until local configuration evidence shows exposure. Mitigation focus: Review Squid and vendor guidance for this CVE before changing production controls.; Audit squid.conf for CONNECT rules that trust req_header Host regex matches.; Avoid relying on client-supplied Host headers as the sole allow decision..

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-2012-2213 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.