{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-1199 exists.","fix":"No fix has been published for CVE-2000-1199 yet. Limit exposure of the affected software until one is available.","what":"CVE-2000-1199 is a medium-severity vulnerability in Postgresql Postgresql, published on 12 Sep 2001."},"fix_prompt":"Check this codebase for CVE-2000-1199 and fix it if it is affected.\n\nWhat it is: CVE-2000-1199 is a medium-severity vulnerability in Postgresql Postgresql, published on 12 Sep 2001. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-1199 exists.\n\nAffected product: Postgresql Postgresql. 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-1199/ (Markdown: https://insights.sbomify.com/CVE-2000-1199/index.md)","id":"CVE-2000-1199","markdown":"https://insights.sbomify.com/CVE-2000-1199/index.md","name":"CVE-2000-1199","record":{"aliases":["GHSA-9ccp-985w-grj6"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["data_read","privilege_escalation"],"network_reachable":"unknown","non_default_config":false,"product_category":"PostgreSQL database","requires_auth":"high_privilege","summary":"Attackers with sufficient privileges can read plaintext credentials from PostgreSQL system tables, leading to database access and privilege escalation.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"postgresql","vendor":"postgresql"}],"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":"PostgreSQL stores usernames and passwords in plaintext in (1) pg_shadow and (2) pg_pwd, which allows attackers with sufficient privileges to gain access to databases.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2000-04-23","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2000-04-23","kind":"exploitdb","ref":"19875","stars":null,"title":"PostgreSQL 6.3.2/6.5.3 - Cleartext Passwords"}],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2000-1199","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"postgresql:postgresql","products":["postgresql:postgresql"],"type":"information_disclosure","year":"2000"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2000-1200"},"packages":[],"prev":{"headline":"Race condition in n/a","id":"CVE-2000-1198"},"products":["n/a"],"published":"2001-09-12","related":[{"cvss_score":10,"headline":"Information disclosure in n/a","id":"CVE-2013-1902","kev_date_added":null,"published":"2013-04-04"},{"cvss_score":10,"headline":"Information disclosure in n/a","id":"CVE-2013-1903","kev_date_added":null,"published":"2013-04-04"},{"cvss_score":10,"headline":"Privilege escalation in n/a","id":"CVE-2007-3279","kev_date_added":null,"published":"2007-06-19"},{"cvss_score":10,"headline":"Integer overflow in n/a","id":"CVE-2002-1399","kev_date_added":null,"published":"2003-01-08"},{"cvss_score":9.1,"headline":"Information disclosure in n/a","id":"CVE-2016-3065","kev_date_added":null,"published":"2016-04-11"},{"cvss_score":9,"headline":"Code injection in n/a","id":"CVE-2007-3280","kev_date_added":null,"published":"2007-06-19"},{"cvss_score":8.8,"headline":"PostgreSQL tsvector and tsquery undersize allocations, via integer wraparound","id":"CVE-2026-14662","kev_date_added":null,"published":"2026-08-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)"},{"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":"Attackers with sufficient privileges can read plaintext credentials from PostgreSQL system tables, leading to database access and privilege escalation.","url":"https://insights.sbomify.com/CVE-2000-1199/"}