# CVE-2006-0591: Weak cryptography in n/a

> Weak salt generation in crypt_blowfish allows attackers to more easily guess passwords from stolen files due to increased collisions.

- **Severity:** Low 1.2 (`AV:L/AC:H/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-prwf-cxjx-w992

## What is CVE-2006-0591?

CVE-2006-0591 is a low-severity vulnerability in n/a, published on 8 Feb 2006. 

### Official description

The crypt_gensalt functions for BSDI-style extended DES-based and FreeBSD-sytle MD5-based password hashes in crypt_blowfish 0.4.7 and earlier do not evenly and randomly distribute salts, which makes it easier for attackers to guess passwords from a stolen password file due to the increased number of collisions.

Weakness: CWE-310

## Which versions are affected by CVE-2006-0591?

It affects 1 product.


Products: Solar Designer Crypt Blowfish.

## How do I fix CVE-2006-0591?

Upgrade to a fixed version.

## Is CVE-2006-0591 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-0591 and fix it if it is affected.

What it is: CVE-2006-0591 is a low-severity vulnerability in n/a, published on 8 Feb 2006. 
Exploitation: There is no known exploitation of CVE-2006-0591 in the wild and no public exploit code.

Affected product: n/a. 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-2006-0591/ (Markdown: https://insights.sbomify.com/CVE-2006-0591/index.md)
```

## Sources

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

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