CVE-2012-2213

What it is

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

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

12.2% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2012-04-28 10:06 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 23:41 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 12.2% in the next 30 days (EPSS).
• Severity: 5.0 MEDIUM (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2012-04-28 10:06 UTC

Last modified

2026-06-16 23:41 UTC

Exploit probability

12.2% · EPSS, next 30 days

Weakness

CWE-264

Record status

Modified

Affected

• squid-cache Squid 3.1.9

Attack profile CVSS 2.0 · 5.0

Attack vector

Network

Complexity

Low

Authentication

None

Confidentiality

Partial

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2012-2213.md and follow it. Check whether this project is affected by CVE-2012-2213. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge