Vulnerability in PostgreSQL
CVE-2002-1657
PostgreSQL uses the username for a salt when generating passwords, which makes it easier for remote attackers to guess passwords via a brute force attack.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
EPSS exploit prediction
EPSS: 0.013 (68.7th percentile), scored .
Low probability of exploitation in the next 30 days, but still tracked. 69th percentile — 68.7% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.013 · newest: 0.013 · change: 0.000
Affected products
- PostgreSQL — versions 7.3.19
Weakness classification (CWE)
References
- exchange.xforce.ibmcloud.com/vulnerabilities/20215 (VDB Entry, vdb-entry, Broken Link)
- marc.info/ (mailing-list, Mailing List)
- marc.info/ (mailing-list, Mailing List)
- archives.postgresql.org/pgsql-admin/2002-08/msg00253.php (mailing-list, Mailing List)
Frequently asked questions
- What is CVE-2002-1657?
- CVE-2002-1657 is a high-severity vulnerability in PostgreSQL, classified under Use of Password Hash With Insufficient Computational Effort. CVSS score: 7.5/10. Published 2002-12-31.
- How severe is CVE-2002-1657?
- High severity. CVSS v3 base score is 7.5 out of 10.