{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2012-2213 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2012-2213 yet. Limit exposure of the affected software until one is available.","what":"CVE-2012-2213 is a medium-severity authentication bypass vulnerability in Squid-Cache Squid, published on 28 Apr 2012. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2012-2213 and fix it if it is affected.\n\nWhat it is: CVE-2012-2213 is a medium-severity authentication bypass vulnerability in Squid-Cache Squid, published on 28 Apr 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2012-2213 in the wild and no public exploit code.\n\nAffected product: Squid-Cache Squid. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2012-2213/ (Markdown: https://insights.sbomify.com/CVE-2012-2213/index.md)","id":"CVE-2012-2213","markdown":"https://insights.sbomify.com/CVE-2012-2213/index.md","name":"CVE-2012-2213","record":{"aliases":["GHSA-4xhr-2rmp-vfjq"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Squid proxy server","requires_auth":"none","summary":"Remote attackers can bypass CONNECT method access controls in Squid by manipulating the Host header, potentially allowing unauthorized proxy usage.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"squid","vendor":"squid-cache"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"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","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Auth bypass in n/a","id":"CVE-2012-2213","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"squid-cache:squid","products":["squid-cache:squid"],"type":"auth_bypass","year":"2012"},"n_packages":0,"n_references":6,"next":{"headline":"Denial of service in n/a","id":"CVE-2012-2214"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2012-2212"},"products":["n/a"],"published":"2012-04-28","related":[{"cvss_score":10,"headline":"Squid vulnerable to information disclosure via authentication credential leakage in error handling","id":"CVE-2025-62168","kev_date_added":null,"published":"2025-10-17"},{"cvss_score":9.3,"headline":"Squid's URN Handling can lead to Buffer Overflow","id":"CVE-2025-54574","kev_date_added":null,"published":"2025-08-01"},{"cvss_score":9.2,"headline":"Squid vulnerable to Denial of Service in ICP Request handling","id":"CVE-2026-33526","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":8.7,"headline":"Squid has Denial of Service in ICP Response handling","id":"CVE-2026-32748","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":8.6,"headline":"SQUID-2023:10 Denial of Service in HTTP Request parsing","id":"CVE-2023-50269","kev_date_added":null,"published":"2023-12-14"},{"cvss_score":8.6,"headline":"Denial of Service in HTTP Message Processing in Squid","id":"CVE-2023-49285","kev_date_added":null,"published":"2023-12-04"},{"cvss_score":8.6,"headline":"Denial of Service in Helper Process management","id":"CVE-2023-49286","kev_date_added":null,"published":"2023-12-04"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["n/a"]},"summary":"Remote attackers can bypass CONNECT method access controls in Squid by manipulating the Host header, potentially allowing unauthorized proxy usage.","url":"https://insights.sbomify.com/CVE-2012-2213/"}