{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2000-0199 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2000-0199 yet. Limit exposure of the affected software until one is available.","what":"CVE-2000-0199 is a high-severity vulnerability in Microsoft Sql Server, published on 22 Mar 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-0199 and fix it if it is affected.\n\nWhat it is: CVE-2000-0199 is a high-severity vulnerability in Microsoft Sql Server, published on 22 Mar 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-0199 in the wild and no public exploit code.\n\nAffected product: Microsoft Sql Server. 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-0199/ (Markdown: https://insights.sbomify.com/CVE-2000-0199/index.md)","id":"CVE-2000-0199","markdown":"https://insights.sbomify.com/CVE-2000-0199/index.md","name":"CVE-2000-0199","record":{"aliases":["GHSA-5xgx-wrh9-vgf4"],"analysis":{"component_type":"database","fix_type":"configuration_change","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"SQL Server Enterprise Manager","requires_auth":"none","summary":"Weak encryption of stored credentials in SQL Server Enterprise Manager allows local attackers to recover login information if the prompt option is disabled.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sql_server","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":"When a new SQL Server is registered in Enterprise Manager for Microsoft SQL Server 7.0 and the \"Always prompt for login name and password\" option is not set, then the Enterprise Manager uses weak encryption to store the login ID and password.","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":"Weak cryptography in n/a","id":"CVE-2000-0199","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:sql_server","products":["microsoft:sql_server"],"type":"weak_cryptography","year":"2000"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2000-0200"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2000-0198"},"products":["n/a"],"published":"2000-03-22","related":[{"cvss_score":9.8,"headline":"Microsoft SQL Server Reporting Services Remote Code Execution","id":"CVE-2020-0618","kev_date_added":"2024-09-18","published":"2020-02-11"},{"cvss_score":8.8,"headline":"Microsoft SQL Server Remote Code Execution","id":"CVE-2019-1068","kev_date_added":"2026-08-26","published":"2019-07-15"},{"cvss_score":9.8,"headline":"Memory corruption in Microsoft SQL Server","id":"CVE-2018-8273","kev_date_added":null,"published":"2018-08-15"},{"cvss_score":9,"headline":"Memory corruption in n/a","id":"CVE-2008-5416","kev_date_added":null,"published":"2008-12-10"},{"cvss_score":8.8,"headline":"Microsoft SQL Server Remote Code Execution Vulnerability","id":"CVE-2023-21705","kev_date_added":null,"published":"2023-02-14"},{"cvss_score":8.8,"headline":"Microsoft SQL Server Remote Code Execution Vulnerability","id":"CVE-2023-21713","kev_date_added":null,"published":"2023-02-14"},{"cvss_score":8.8,"headline":"Microsoft SQL Elevation of Privilege Vulnerability","id":"CVE-2021-1636","kev_date_added":null,"published":"2021-01-12"}],"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":"Weak encryption of stored credentials in SQL Server Enterprise Manager allows local attackers to recover login information if the prompt option is disabled.","url":"https://insights.sbomify.com/CVE-2000-0199/"}