Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2000-0445 | First vendor Publication | 2000-05-24 |
| Vendor | Cve | Last vendor Modification | 2024-11-20 |
Security-Database Scoring CVSS v3
| Cvss vector : N/A | |||
|---|---|---|---|
| Overall CVSS Score | NA | ||
| Base Score | NA | Environmental Score | NA |
| impact SubScore | NA | Temporal Score | NA |
| Exploitabality Sub Score | NA | ||
| Calculate full CVSS 3.0 Vectors scores | |||
Security-Database Scoring CVSS v2
| Cvss vector : (AV:L/AC:L/Au:N/C:P/I:N/A:N) | |||
|---|---|---|---|
| Cvss Base Score | 2.1 | Attack Range | Local |
| Cvss Impact Score | 2.9 | Attack Complexity | Low |
| Cvss Expoit Score | 3.9 | Authentication | None Required |
| Calculate full CVSS 2.0 Vectors scores | |||
Detail
| 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. |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2000-0445 |
CPE : Common Platform Enumeration
| Type | Description | Count |
|---|---|---|
| Application | 3 |
Open Source Vulnerability Database (OSVDB)
| Id | Description |
|---|---|
| 1355 | PGP Predictable Key Generation PGP contains a flaw that may cause public and private keys to be generated without sufficient randomness potentially compromising the integrity and strength of the keys. The issue is due to a flaw in the "pgpk" program and it's reliance on /dev/random for entropy/randomness when creating new key pairs. If a user fails to use a long pass phrase and fails to input characters when prompted, the strength of the key pair may be significantly weakened to allow for cryptographic attack against the key pair. |
Sources (Detail)
| Source | Url |
|---|
Alert History
| Date | Informations |
|---|---|
| 2024-11-28 23:24:45 |
|
| 2024-11-28 12:04:08 |
|
| 2021-05-04 12:01:09 |
|
| 2021-04-22 01:01:21 |
|
| 2020-05-23 00:14:23 |
|
| 2016-06-28 14:52:51 |
|
| 2013-05-11 12:00:15 |
|
