Vulnerability Description
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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Postgresql | Postgresql | 7.3.19 |
Related Weaknesses (CWE)
References
- http://archives.postgresql.org/pgsql-admin/2002-08/msg00253.phpMailing List
- http://marc.info/?l=bugtraq&m=111402558115859&w=2Mailing List
- http://marc.info/?l=bugtraq&m=111403050902165&w=2Mailing List
- https://exchange.xforce.ibmcloud.com/vulnerabilities/20215Broken LinkVDB Entry
- http://archives.postgresql.org/pgsql-admin/2002-08/msg00253.phpMailing List
- http://marc.info/?l=bugtraq&m=111402558115859&w=2Mailing List
- http://marc.info/?l=bugtraq&m=111403050902165&w=2Mailing List
- https://exchange.xforce.ibmcloud.com/vulnerabilities/20215Broken LinkVDB Entry
FAQ
What is CVE-2002-1657?
CVE-2002-1657 is a vulnerability with a CVSS score of 7.5 (HIGH). 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.
How severe is CVE-2002-1657?
CVE-2002-1657 has been rated HIGH with a CVSS base score of 7.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2002-1657?
Check the references section above for vendor advisories and patch information. Affected products include: Postgresql Postgresql.