{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2011-4197 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2011-4197 yet. Limit exposure of the affected software until one is available.","what":"CVE-2011-4197 is a high-severity vulnerability in n/a, published on 3 Jan 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-2011-4197 and fix it if it is affected.\n\nWhat it is: CVE-2011-4197 is a high-severity vulnerability in n/a, published on 3 Jan 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-2011-4197 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2011-4197/ (Markdown: https://insights.sbomify.com/CVE-2011-4197/index.md)","id":"CVE-2011-4197","markdown":"https://insights.sbomify.com/CVE-2011-4197/index.md","name":"CVE-2011-4197","record":{"aliases":["GHSA-wprp-q629-mgxj"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"pfSense firewall","requires_auth":"none","summary":"Remote attackers can forge sub-certificates for arbitrary subjects due to incorrect CA basic constraints in pfSense PKI implementation.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pfsense","vendor":"pfsense"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"etc/inc/certs.inc in the PKI implementation in pfSense before 2.0.1 creates each X.509 certificate with a true value for the CA basic constraint, which allows remote attackers to create sub-certificates for arbitrary subjects by leveraging the private key.","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":"Security feature bypass in n/a","id":"CVE-2011-4197","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2011"},"n_packages":0,"n_references":8,"next":{"headline":"Command injection in n/a","id":"CVE-2011-4201"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2011-4195"},"products":["n/a"],"published":"2012-01-03","related":[{"cvss_score":9.9,"headline":"Code injection in n/a","id":"CVE-2025-69691","kev_date_added":null,"published":"2026-05-08"},{"cvss_score":9.8,"headline":"Weak cryptography in n/a","id":"CVE-2023-29974","kev_date_added":null,"published":"2023-11-08"},{"cvss_score":9.1,"headline":"Deserialization in n/a","id":"CVE-2025-69690","kev_date_added":null,"published":"2026-05-08"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2021-41282","kev_date_added":null,"published":"2022-03-01"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2016-10709","kev_date_added":null,"published":"2018-01-22"},{"cvss_score":8.6,"headline":"Netgate pfSense CE 2.7.0 through 2.9.0 OS Command Injection via interfaces_qinq_edit.php","id":"CVE-2026-111214","kev_date_added":null,"published":"2026-10-15"},{"cvss_score":8.6,"headline":"Netgate pfSense CE through 2.9.0 OS Command Injection via Wireless Parent Interface","id":"CVE-2026-111215","kev_date_added":null,"published":"2026-10-15"}],"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-08-07","vendors":["n/a"]},"summary":"Remote attackers can forge sub-certificates for arbitrary subjects due to incorrect CA basic constraints in pfSense PKI implementation.","url":"https://insights.sbomify.com/CVE-2011-4197/"}