{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-3209 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-3209 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-3209 is a high-severity vulnerability in Microsoft Windows Xp, published on 24 Jun 2006. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2006-3209 and fix it if it is affected.\n\nWhat it is: CVE-2006-3209 is a high-severity vulnerability in Microsoft Windows Xp, published on 24 Jun 2006. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2006-3209 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-3209/ (Markdown: https://insights.sbomify.com/CVE-2006-3209/index.md)","id":"CVE-2006-3209","markdown":"https://insights.sbomify.com/CVE-2006-3209/index.md","name":"CVE-2006-3209","record":{"aliases":["GHSA-4c2h-m2v8-77j8"],"analysis":{"component_type":"operating_system","fix_type":"no_fix_stated","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Windows Task Scheduler","requires_auth":"low_privilege","summary":"Local users can gain SYSTEM privileges via the Windows Task Scheduler, though this is disputed as requiring Administrator access by default.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"windows_xp","vendor":"microsoft"}],"cvss":{"score":7.2,"severity":"high","source":"nvd","vector":"AV:L/AC:L/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"The Task scheduler (at.exe) on Microsoft Windows XP spawns each scheduled process with SYSTEM permissions, which allows local users to gain privileges.  NOTE: this issue has been disputed by third parties, who state that the Task scheduler is limited to the Administrators group by default upon installation","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":"Privilege escalation in n/a","id":"CVE-2006-3209","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:windows_xp","products":["microsoft:windows_xp"],"type":"privilege_escalation","year":"2006"},"n_packages":0,"n_references":3,"next":{"headline":"Code injection in n/a","id":"CVE-2006-3210"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2006-3208"},"products":["n/a"],"published":"2006-06-24","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 users can gain SYSTEM privileges via the Windows Task Scheduler, though this is disputed as requiring Administrator access by default.","url":"https://insights.sbomify.com/CVE-2006-3209/"}