{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-1476 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-1476 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-1476 is a low-severity vulnerability in Microsoft Windows Xp, published on 29 Mar 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2006-1476 and fix it if it is affected.\n\nWhat it is: CVE-2006-1476 is a low-severity vulnerability in Microsoft Windows Xp, published on 29 Mar 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2006-1476 in the wild and no public exploit code.\n\nAffected product: Microsoft Windows Xp. 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-2006-1476/ (Markdown: https://insights.sbomify.com/CVE-2006-1476/index.md)","id":"CVE-2006-1476","markdown":"https://insights.sbomify.com/CVE-2006-1476/index.md","name":"CVE-2006-1476","record":{"aliases":["GHSA-7cgp-frq2-2r3w"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Windows Firewall","requires_auth":"low_privilege","summary":"Local attackers can trick users into unblocking malicious executables by exploiting Windows Firewall alert naming flaws.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"windows_xp","vendor":"microsoft"}],"cvss":{"score":2.6,"severity":"low","source":"nvd","vector":"AV:N/AC:H/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[],"description":"Windows Firewall in Microsoft Windows XP SP2 produces incorrect application block alerts when the application filename is \".exe\" (with no characters before the \".\"), which might allow local user-assisted users to trick a user into unblocking a Trojan horse program, as demonstrated by a malicious \".exe\" program in a folder named \"Internet Explorer,\" which triggers a question about whether to unblock the \"Internet Explorer\" program.","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-2006-1476","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:windows_xp","products":["microsoft:windows_xp"],"type":"security_feature_bypass","year":"2006"},"n_packages":0,"n_references":3,"next":{"headline":"Code injection in n/a","id":"CVE-2006-1477"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2006-1475"},"products":["n/a"],"published":"2006-03-29","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2012-1852","kev_date_added":null,"published":"2012-08-15"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2012-1853","kev_date_added":null,"published":"2012-08-15"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2009-0119","kev_date_added":null,"published":"2009-01-14"},{"cvss_score":10,"headline":"Integer overflow in n/a","id":"CVE-2007-1946","kev_date_added":null,"published":"2007-04-11"},{"cvss_score":10,"headline":"Hardcoded credentials in n/a","id":"CVE-2005-3595","kev_date_added":null,"published":"2005-11-16"},{"cvss_score":10,"headline":"Code injection in n/a","id":"CVE-2004-2289","kev_date_added":null,"published":"2005-08-04"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2013-1313","kev_date_added":null,"published":"2013-02-13"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Local attackers can trick users into unblocking malicious executables by exploiting Windows Firewall alert naming flaws.","url":"https://insights.sbomify.com/CVE-2006-1476/"}