{"answers":{"affected":"It affects 4 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-1209 exists.","fix":"No fix has been published for CVE-2000-1209 yet. Limit exposure of the affected software until one is available.","what":"CVE-2000-1209 is a critical vulnerability in n/a, published on 10 Aug 2002. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2000-1209 and fix it if it is affected.\n\nWhat it is: CVE-2000-1209 is a critical vulnerability in n/a, published on 10 Aug 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-1209 exists.\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-2000-1209/ (Markdown: https://insights.sbomify.com/CVE-2000-1209/index.md)","id":"CVE-2000-1209","markdown":"https://insights.sbomify.com/CVE-2000-1209/index.md","name":"CVE-2000-1209","record":{"aliases":["GHSA-hwwv-vx36-7jpp"],"analysis":{"component_type":"database","fix_type":"configuration_change","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Microsoft SQL Server","requires_auth":"none","summary":"Remote attackers can gain privileges and execute code by exploiting the default null password on the sa account in Microsoft SQL Server.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"insight_manager","vendor":"compaq"},{"product":"insight_manager_xe","vendor":"compaq"},{"product":"data_engine","vendor":"microsoft"},{"product":"msde","vendor":"microsoft"}],"cvss":{"score":10,"severity":"critical","source":"nvd","vector":"AV:N/AC:L/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"The \"sa\" account is installed with a default null password on (1) Microsoft SQL Server 2000, (2) SQL Server 7.0, and (3) Data Engine (MSDE) 1.0, including third party packages that use these products such as (4) Tumbleweed Secure Mail (MMS) (5) Compaq Insight Manager, and (6) Visio 2000, which allows remote attackers to gain privileges, as exploited by worms such as Voyager Alpha Force and Spida.","ecosystems":[],"exploits":{"exploitdb":2,"first_seen":"2000-05-30","github_poc":0,"max_poc_stars":null,"metasploit":2,"nuclei":0,"refs":[{"date":"2000-05-30","kind":"metasploit","ref":"exploit/windows/mssql/mssql_payload","stars":null,"title":"Microsoft SQL Server Payload Execution"},{"date":"2000-05-30","kind":"metasploit","ref":"exploit/windows/mssql/mssql_payload_sqli","stars":null,"title":"Microsoft SQL Server Payload Execution via SQL Injection"},{"date":"2010-12-21","kind":"exploitdb","ref":"16395","stars":null,"title":"Microsoft SQL Server - Payload Execution (Metasploit)"},{"date":"2011-02-08","kind":"exploitdb","ref":"16394","stars":null,"title":"Microsoft SQL Server - Payload Execution (via SQL Injection) (Metasploit)"}],"tier":"weaponised"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2000-1209","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2000"},"n_packages":0,"n_references":12,"next":{"headline":"Apache Tomcat Directory Traversal","id":"CVE-2000-1210"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2000-1208"},"products":["n/a"],"published":"2002-08-10","related":[],"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)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"Remote attackers can gain privileges and execute code by exploiting the default null password on the sa account in Microsoft SQL Server.","url":"https://insights.sbomify.com/CVE-2000-1209/"}