# CVE-2002-1657: Weak cryptography in n/a

> PostgreSQL uses the username as a password salt, weakening password security and facilitating brute-force attacks against user credentials.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2005
- **Updated:** 16 Jan 2025
- **Also known as:** GHSA-vjwv-wcj8-hxqj

## What is CVE-2002-1657?

CVE-2002-1657 is a high-severity vulnerability in Postgresql Postgresql, published on 22 Apr 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-916 (Use of Password Hash With Insufficient Computational Effort)

## Which versions are affected by CVE-2002-1657?

It affects 1 product.


Products: Postgresql Postgresql.

## How do I fix CVE-2002-1657?

No fix has been published for CVE-2002-1657 yet. Limit exposure of the affected software until one is available.

## Is CVE-2002-1657 being exploited?

There is no known exploitation of CVE-2002-1657 in the wild and no public exploit code.

## Other vulnerabilities in Postgresql Postgresql

- [CVE-2013-1902](https://insights.sbomify.com/CVE-2013-1902/): Information disclosure in n/a (critical 10.0)
- [CVE-2013-1903](https://insights.sbomify.com/CVE-2013-1903/): Information disclosure in n/a (critical 10.0)
- [CVE-2007-3279](https://insights.sbomify.com/CVE-2007-3279/): Privilege escalation in n/a (critical 10.0)
- [CVE-2002-1399](https://insights.sbomify.com/CVE-2002-1399/): Integer overflow in n/a (critical 10.0)
- [CVE-2016-3065](https://insights.sbomify.com/CVE-2016-3065/): Information disclosure in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1657 and fix it if it is affected.

What it is: CVE-2002-1657 is a high-severity vulnerability in Postgresql Postgresql, published on 22 Apr 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-1657 in the wild and no public exploit code.

Affected product: Postgresql Postgresql. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2002-1657/ (Markdown: https://insights.sbomify.com/CVE-2002-1657/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2002-1657
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2002-1657
- OSV: https://osv.dev/vulnerability/CVE-2002-1657

---
From sbomify Insights: https://insights.sbomify.com/CVE-2002-1657/
Summaries are generated and may contain mistakes; the official description above is the record.