# CVE-2001-1467: Weak cryptography in n/a

> Weak random seeding in mkpasswd allows attackers to brute force passwords more easily due to limited seed space.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Apr 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-f6m6-f2pm-2grw

## What is CVE-2001-1467?

CVE-2001-1467 is a high-severity vulnerability in n/a, published on 21 Apr 2005. 

### Official description

mkpasswd in expect 5.2.8, as used by Red Hat Linux 6.2 through 7.0, seeds its random number generator with its process ID, which limits the space of possible seeds and makes it easier for attackers to conduct brute force password attacks.

## Which versions are affected by CVE-2001-1467?

It affects 1 product.


Products: Don Libes Expect.

## How do I fix CVE-2001-1467?

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

## Is CVE-2001-1467 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-1467 and fix it if it is affected.

What it is: CVE-2001-1467 is a high-severity vulnerability in n/a, published on 21 Apr 2005. 
Exploitation: There is no known exploitation of CVE-2001-1467 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-2001-1467/ (Markdown: https://insights.sbomify.com/CVE-2001-1467/index.md)
```

## Sources

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

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