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
CVE-2012-2213
NONECVSS 0.0Elevated
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 12%CVSS: —Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- —
- EG Score
- 0.0(none)
- EPSS
- 95.7%
- KEV
- Not listed
Published
April 28, 2012
Last Modified
April 29, 2026
References (12)
- cve@mitrehttp://archives.neohapsis.com/archives/bugtraq/2012-04/0117.html
- cve@mitrehttp://archives.neohapsis.com/archives/bugtraq/2012-04/0131.html
- cve@mitrehttp://archives.neohapsis.com/archives/bugtraq/2012-04/0140.html
- cve@mitrehttp://archives.neohapsis.com/archives/bugtraq/2012-04/0146.html
- cve@mitrehttp://archives.neohapsis.com/archives/bugtraq/2012-04/0163.html
- cve@mitrehttp://archives.neohapsis.com/archives/bugtraq/2012-04/0165.html
- af854a3a-2127-422b-91ae-364da2661108http://archives.neohapsis.com/archives/bugtraq/2012-04/0117.html
- af854a3a-2127-422b-91ae-364da2661108http://archives.neohapsis.com/archives/bugtraq/2012-04/0131.html
- af854a3a-2127-422b-91ae-364da2661108http://archives.neohapsis.com/archives/bugtraq/2012-04/0140.html
- af854a3a-2127-422b-91ae-364da2661108http://archives.neohapsis.com/archives/bugtraq/2012-04/0146.html
- af854a3a-2127-422b-91ae-364da2661108http://archives.neohapsis.com/archives/bugtraq/2012-04/0163.html
- af854a3a-2127-422b-91ae-364da2661108http://archives.neohapsis.com/archives/bugtraq/2012-04/0165.html
Frequently asked(4)
What is CVE-2012-2213?
CVE-2012-2213 is a none vulnerability published on April 28, 2012. 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…
When was CVE-2012-2213 disclosed?
CVE-2012-2213 was first published in the National Vulnerability Database on April 28, 2012, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2012-2213 actively exploited?
CVE-2012-2213 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 95.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2012-2213?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2012-2213, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2012-2213
Is Your Infrastructure Affected by CVE-2012-2213?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.