CVE-2000-0445 Weak cryptography in n/a
Low 2.1
Published
Updated
Check this codebase for CVE-2000-0445 and fix it if it is affected.
What it is: CVE-2000-0445 is a low-severity vulnerability in n/a, published on 13 Oct 2000.
Exploitation: There is no known exploitation of CVE-2000-0445 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-2000-0445/ (Markdown: https://insights.sbomify.com/CVE-2000-0445/index.md)
Insufficient randomness in PGP key generation allows attackers to predict keys, compromising encrypted data confidentiality.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2000-0445?
CVE-2000-0445 is a low-severity vulnerability in n/a, published on 13 Oct 2000.
Official description
The pgpk command in PGP 5.x on Unix systems uses an insufficiently random data source for non-interactive key pair generation, which may produce predictable keys.
Which versions are affected by CVE-2000-0445?
It affects 1 product.
Products include Pgp Pgp.
How do I fix CVE-2000-0445?
No fix has been published for CVE-2000-0445 yet. Limit exposure of the affected software until one is available.
Is CVE-2000-0445 being exploited?
There is no known exploitation of CVE-2000-0445 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-r4m8-4q3x-xfcc.