GNU GNU Privacy Guard 1.0.2
Approved changes feed: RSS · Atom
cpe:2.3:a:gnu:privacy_guard:1.0.2:*:*:*:*:*:*:*
part: a version: 1.0.2 update: *
| Vendor | Gnu (575dd98a-a14a-5d9e-a2eb-97d38d86fcb9) |
|---|---|
| Product | Privacy Guard (9a3678db-31d6-5a6b-9731-d81acc8d3ee5) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:deb/debian/gnupg2 |
purl2cpe | 2026-06-01 10:11:56.469512 |
pkg:deb/ubuntu/gnupg2 |
purl2cpe | 2026-06-01 10:11:56.469513 |
pkg:github/gpg/gnupg |
purl2cpe | 2026-06-01 10:11:56.469515 |
pkg:gitlab/redhat/gnupg2 |
purl2cpe | 2026-06-01 10:11:56.469516 |
pkg:rpm/centos/gnupg2 |
purl2cpe | 2026-06-01 10:11:56.469518 |
pkg:rpm/fedora/gnupg2 |
purl2cpe | 2026-06-01 10:11:56.469519 |
pkg:rpm/opensuse/gnupg2 |
purl2cpe | 2026-06-01 10:11:56.469520 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2006-0455 |
vulnerable | 2026-06-08 04:48:53.930204 |
Details available
gpgv in GnuPG before 1.4.2.1, when using unattended signature verification, returns a 0 exit code in certain cases even when the detached signature file does not carry a signature, which could cause programs that use gpgv to assume that the signature verification has succeeded. Note: this also occurs when running the equivalent command "gpg --verify".
Published: 2006-02-15T22:00:00.000Z
Updated: 2024-08-07T16:34:14.838Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2006-0049 |
vulnerable | 2026-06-08 04:48:45.800853 |
Details available
gpg in GnuPG before 1.4.2.2 does not properly verify non-detached signatures, which allows attackers to inject unsigned data via a data packet that is not associated with a control packet, which causes the check for concatenated signatures to report that the signature is valid, a different vulnerability than CVE-2006-0455.
Published: 2006-03-13T21:00:00.000Z
Updated: 2024-08-07T16:18:20.663Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2003-0971 |
vulnerable | 2026-06-08 04:47:22.941859 |
Details available
GnuPG (GPG) 1.0.2, and other versions up to 1.2.3, creates ElGamal type 20 (sign+encrypt) keys using the same key component for encryption as for signing, which allows attackers to determine the private key from a signature.
Published: 2003-12-02T05:00:00.000Z
Updated: 2024-08-08T02:12:35.614Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2001-0072 |
vulnerable | 2026-06-08 04:45:19.672743 |
Details available
gpg (aka GnuPG) 1.0.4 and other versions imports both public and private keys from public key servers without notifying the user about the private keys, which could allow an attacker to break the web of trust.
Published: 2001-05-07T04:00:00.000Z
Updated: 2024-08-08T04:06:54.929Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2001-0071 |
vulnerable | 2026-06-08 04:45:19.671192 |
Details available
gpg (aka GnuPG) 1.0.4 and other versions does not properly verify detached signatures, which allows attackers to modify the contents of a file without detection.
Published: 2001-05-07T04:00:00.000Z
Updated: 2024-08-08T04:06:55.235Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2000-0974 |
vulnerable | 2026-06-08 04:45:19.056848 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.