# CVE-2000-1199: Information disclosure in n/a

> Attackers with sufficient privileges can read plaintext credentials from PostgreSQL system tables, leading to database access and privilege escalation.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Sep 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-9ccp-985w-grj6

## What is CVE-2000-1199?

CVE-2000-1199 is a medium-severity vulnerability in Postgresql Postgresql, published on 12 Sep 2001. 

### Official 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.

## Which versions are affected by CVE-2000-1199?

It affects 1 product.


Products: Postgresql Postgresql.

## How do I fix CVE-2000-1199?

No fix has been published for CVE-2000-1199 yet. Limit exposure of the affected software until one is available.

## Is CVE-2000-1199 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-1199 exists.

Public exploit code:

- PostgreSQL 6.3.2/6.5.3 - Cleartext Passwords (exploitdb)

## Other vulnerabilities in Postgresql Postgresql

- [CVE-2013-1902](https://insights.sbomify.com/CVE-2013-1902/): Information disclosure in n/a (critical 10.0)
- [CVE-2013-1903](https://insights.sbomify.com/CVE-2013-1903/): Information disclosure in n/a (critical 10.0)
- [CVE-2007-3279](https://insights.sbomify.com/CVE-2007-3279/): Privilege escalation in n/a (critical 10.0)
- [CVE-2002-1399](https://insights.sbomify.com/CVE-2002-1399/): Integer overflow in n/a (critical 10.0)
- [CVE-2016-3065](https://insights.sbomify.com/CVE-2016-3065/): Information disclosure in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-1199 and fix it if it is affected.

What it is: CVE-2000-1199 is a medium-severity vulnerability in Postgresql Postgresql, published on 12 Sep 2001. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-1199 exists.

Affected product: Postgresql Postgresql. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2000-1199/ (Markdown: https://insights.sbomify.com/CVE-2000-1199/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2000-1199
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2000-1199
- OSV: https://osv.dev/vulnerability/CVE-2000-1199

---
From sbomify Insights: https://insights.sbomify.com/CVE-2000-1199/
Summaries are generated and may contain mistakes; the official description above is the record.