How severe is CVE-2000-1199?

CVE-2000-1199 has a CVSS 2.0 base score of 4.6, rated medium severity.

Is CVE-2000-1199 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (56th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2000-1199?

CVE-2000-1199 primarily affects Postgresql. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2000-1199?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2000-1199 published?

CVE-2000-1199 was published on 2001-08-31 and last updated on 2026-06-16.

CVE-2000-1199

CVE-2000-1199 is a medium-severity vulnerability in Postgresql with a CVSS 2.0 base score of 4.6. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 2.0 base score 4.6)
EPSS exploit prediction: 1% (56th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Postgresql
Published: 2001-08-31
Last modified: 2026-06-16

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.

Frequently asked questions

What is CVE-2000-1199?: 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.
How severe is CVE-2000-1199?: CVE-2000-1199 has a CVSS 2.0 base score of 4.6, rated medium severity.
Is CVE-2000-1199 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (56th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2000-1199?: CVE-2000-1199 primarily affects Postgresql. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2000-1199?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2000-1199 published?: CVE-2000-1199 was published on 2001-08-31 and last updated on 2026-06-16.

References

Affected products (2)

cpe:2.3:a:postgresql:postgresql:6.3.2:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:6.5.3:*:*:*:*:*:*:*