How severe is CVE-2002-1657?

CVE-2002-1657 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2002-1657 being actively exploited?

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

What products are affected by CVE-2002-1657?

CVE-2002-1657 affects Postgresql. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2002-1657?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2002-1657 published?

CVE-2002-1657 was published on 2002-12-31 and last updated on 2026-06-16.

CVE-2002-1657

CVE-2002-1657 is a high-severity vulnerability in Postgresql with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-916.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 5.0
EPSS exploit prediction: 1% (66th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-916
Affected product: Postgresql
Published: 2002-12-31
Last modified: 2026-06-16

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.

Frequently asked questions

What is 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.
How severe is CVE-2002-1657?: CVE-2002-1657 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2002-1657 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (66th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2002-1657?: CVE-2002-1657 affects Postgresql. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2002-1657?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2002-1657 published?: CVE-2002-1657 was published on 2002-12-31 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:postgresql:postgresql:7.3.19:*:*:*:*:*:*:*

Other CWE-916 vulnerabilities

CVE-2020-14516 — Critical (CVSS 10.0): In Rockwell Automation FactoryTalk Services Platform Versions 6.10.00 and 6.11.00, there is an issue with the…
CVE-2026-30789 — Critical (CVSS 9.8): Use of Password Hash With Insufficient Computational Effort, Improper Restriction of Excessive Authentication Attempts…
CVE-2024-5743 — Critical (CVSS 9.8): An attacker could exploit the 'Use of Password Hash With Insufficient Computational Effort' vulnerability in EveHome…
CVE-2021-36767 — Critical (CVSS 9.8): In Digi RealPort through 4.10.490, authentication relies on a challenge-response mechanism that gives access to the…
CVE-2021-32519 — Critical (CVSS 9.8): Use of password hash with insufficient computational effort vulnerability in QSAN Storage Manager, XEVO, SANOS allows…
CVE-2019-17216 — Critical (CVSS 9.8): An issue was discovered on V-Zug Combi-Steam MSLQ devices before Ethernet R07 and before WLAN R05. Password…

Browse all CWE-916 vulnerabilities →