{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2000-0663 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2000-0663 yet. Limit exposure of the affected software until one is available.","what":"CVE-2000-0663 is a medium-severity path traversal vulnerability in Microsoft Windows 2000, published on 13 Oct 2000. 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-2000-0663 and fix it if it is affected.\n\nWhat it is: CVE-2000-0663 is a medium-severity path traversal vulnerability in Microsoft Windows 2000, published on 13 Oct 2000. 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-2000-0663 in the wild and no public exploit code.\n\nAffected product: Microsoft Windows 2000. 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-2000-0663/ (Markdown: https://insights.sbomify.com/CVE-2000-0663/index.md)","id":"CVE-2000-0663","markdown":"https://insights.sbomify.com/CVE-2000-0663/index.md","name":"CVE-2000-0663","record":{"aliases":["GHSA-527c-22g3-c82g"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Windows OS","requires_auth":"low_privilege","summary":"Local attackers can execute arbitrary code by placing a malicious Explorer.exe in the system drive due to relative path usage in the Windows Shell registry entry.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"windows_2000","vendor":"microsoft"},{"product":"windows_nt","vendor":"microsoft"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"The registry entry for the Windows Shell executable (Explorer.exe) in Windows NT and Windows 2000 uses a relative path name, which allows local users to execute arbitrary commands by inserting a Trojan Horse named Explorer.exe into the %Systemdrive% directory, aka the \"Relative Shell Path\" vulnerability.","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":"Path traversal in n/a","id":"CVE-2000-0663","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:windows_2000","products":["microsoft:windows_2000","microsoft:windows_nt"],"type":"path_traversal","year":"2000"},"n_packages":0,"n_references":4,"next":{"headline":"Path traversal in n/a","id":"CVE-2000-0664"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2000-0662"},"products":["n/a"],"published":"2000-10-13","related":[{"cvss_score":9.8,"headline":"Microsoft Windows Buffer Overflow","id":"CVE-2008-4250","kev_date_added":"2026-05-20","published":"2008-10-23"},{"cvss_score":7.8,"headline":"Microsoft Windows Kernel Exception Handler","id":"CVE-2010-0232","kev_date_added":"2022-03-03","published":"2010-01-21"},{"cvss_score":7.8,"headline":"Microsoft Windows Improper Input Validation","id":"CVE-2009-1123","kev_date_added":"2022-03-03","published":"2009-06-10"},{"cvss_score":7.8,"headline":"Microsoft Windows Privilege Escalation","id":"CVE-2002-0367","kev_date_added":"2022-03-03","published":"2003-04-02"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2010-0269","kev_date_added":null,"published":"2010-04-14"},{"cvss_score":10,"headline":"Weak cryptography in n/a","id":"CVE-2010-0231","kev_date_added":null,"published":"2010-02-10"},{"cvss_score":10,"headline":"Auth bypass in n/a","id":"CVE-2009-3677","kev_date_added":null,"published":"2009-12-09"}],"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-08","vendors":["n/a"]},"summary":"Local attackers can execute arbitrary code by placing a malicious Explorer.exe in the system drive due to relative path usage in the Windows Shell registry entry.","url":"https://insights.sbomify.com/CVE-2000-0663/"}