CVE-2000-1199: Medium severity PostgreSQL postgresql vulnerability

Published Aug 31, 2001
·
Updated

PostgreSQL stores usernames and passwords in plaintext in (1) pgshadow and (2) pgpwd, which allows attackers with sufficient privileges to gain access to databases.

Affected Software

2 affected components
PostgreSQL postgresql=6.3.2
PostgreSQL postgresql=6.5.3

Event History

Aug 31, 2001
CVE Published
04:00 AM
Sep 12, 2001
CVE Published
via MITRE·04:00 AM
Data Sourced
via MITRE·04:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2000-1199?

CVE-2000-1199 is considered a critical vulnerability due to the exposure of plaintext passwords leading to potential unauthorized database access.

2

How do I fix CVE-2000-1199?

To fix CVE-2000-1199, upgrade to a PostgreSQL version that does not store passwords in plaintext.

3

Which versions of PostgreSQL are affected by CVE-2000-1199?

CVE-2000-1199 affects PostgreSQL versions 6.3.2 and 6.5.3.

4

What are the implications of CVE-2000-1199?

The implications of CVE-2000-1199 include potential attackers being able to easily retrieve sensitive database credentials.

5

Who can exploit CVE-2000-1199?

CVE-2000-1199 can be exploited by anyone with sufficient privileges to access the PostgreSQL database system.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203