CVE-2002-1657
First published: Tue Dec 31 2002(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| PostgreSQL Common | =7.3.19 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2002-1657?
CVE-2002-1657 is considered a medium severity vulnerability due to the potential for password guessing by attackers.
How does CVE-2002-1657 impact PostgreSQL security?
CVE-2002-1657 allows attackers to use predictable salts based on usernames, making it easier to brute force passwords.
What versions of PostgreSQL are affected by CVE-2002-1657?
CVE-2002-1657 specifically affects PostgreSQL version 7.3.19.
How do I fix CVE-2002-1657?
To mitigate CVE-2002-1657, upgrade PostgreSQL to a version that does not use usernames as salts for password hashing.
Can CVE-2002-1657 be exploited remotely?
Yes, CVE-2002-1657 can be exploited remotely, allowing attackers to attempt password guessing attacks from an external location.
- agent/references
- agent/type
- agent/first-publish-date
- agent/severity
- agent/weakness
- agent/description
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- agent/author
- agent/softwarecombine
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-index
- collector/nvd-historical
- vendor/postgresql
- canonical/postgresql common
- version/postgresql common/7.3.19