# CVE-2005-4730: Weak cryptography in n/a

> Predictable random number generation in PEAR Text_Password may allow attackers to bypass security controls relying on this library.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 14 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hw2j-hpjq-wvhv

## What is CVE-2005-4730?

CVE-2005-4730 is a critical vulnerability in n/a, published on 14 Mar 2006. 

### Official description

Unspecified vulnerability in PEAR Text_Password 1.0 has unknown impact and attack vectors, related to "problematic seeding" of the random number generator, possibly predictable seeds.

## Which versions are affected by CVE-2005-4730?

It affects 1 product.


Products: Pear Text Password.

## How do I fix CVE-2005-4730?

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

## Is CVE-2005-4730 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4730 and fix it if it is affected.

What it is: CVE-2005-4730 is a critical vulnerability in n/a, published on 14 Mar 2006. 
Exploitation: There is no known exploitation of CVE-2005-4730 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-2005-4730/ (Markdown: https://insights.sbomify.com/CVE-2005-4730/index.md)
```

## Sources

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

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