GnuPG 1.x before 1.4.16 generates RSA keys using sequences of introductions with certain patterns that introduce a side channel, which allows physically proximate attackers to extract RSA keys via a chosen-ciphertext attack and acoustic cryptanalysis during decryption. NOTE: applications are not typically expected to protect themselves from acoustic side-channel attacks, since this is arguably the responsibility of the physical device. Accordingly, issues of this type would not normally receive a CVE identifier. However, for this issue, the developer has specified a security policy in which GnuPG should offer side-channel resistance, and developer-specified security-policy violations are within the scope of CVE.
CVE-2013-4576 is a security vulnerability that . Impacting 1 product from gnupg organizations running these solutions should prioritize assessment and patching.
Documented in 2013, this vulnerability occurred amid the cloud computing expansion era, where traditional network perimeter security models were being reevaluated. Organizations were transitioning from isolated infrastructure to interconnected systems, creating new attack surfaces that vulnerabilities like this could exploit.
2013-12-20T21:55:06.930
2026-04-29T01:13:23.040
Modified
CVSSv2: 2.1 (LOW)
AV:L/AC:L/Au:N/C:P/I:N/A:N
3.9
2.9
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | gnupg | gnupg | ≤ 1.4.15 | Yes |
| Application | gnupg | gnupg | 1.0.0 | Yes |
| Application | gnupg | gnupg | 1.0.1 | Yes |
| Application | gnupg | gnupg | 1.0.2 | Yes |
| Application | gnupg | gnupg | 1.0.3 | Yes |
| Application | gnupg | gnupg | 1.0.4 | Yes |
| Application | gnupg | gnupg | 1.0.4 | Yes |
| Application | gnupg | gnupg | 1.0.5 | Yes |
| Application | gnupg | gnupg | 1.0.5 | Yes |
| Application | gnupg | gnupg | 1.0.6 | Yes |
| Application | gnupg | gnupg | 1.0.7 | Yes |
| Application | gnupg | gnupg | 1.2.0 | Yes |
| Application | gnupg | gnupg | 1.2.1 | Yes |
| Application | gnupg | gnupg | 1.2.1 | Yes |
| Application | gnupg | gnupg | 1.2.2 | Yes |
| Application | gnupg | gnupg | 1.2.3 | Yes |
| Application | gnupg | gnupg | 1.2.4 | Yes |
| Application | gnupg | gnupg | 1.2.5 | Yes |
| Application | gnupg | gnupg | 1.2.6 | Yes |
| Application | gnupg | gnupg | 1.2.7 | Yes |
| Application | gnupg | gnupg | 1.3.0 | Yes |
| Application | gnupg | gnupg | 1.3.1 | Yes |
| Application | gnupg | gnupg | 1.3.2 | Yes |
| Application | gnupg | gnupg | 1.3.3 | Yes |
| Application | gnupg | gnupg | 1.3.4 | Yes |
| Application | gnupg | gnupg | 1.3.6 | Yes |
| Application | gnupg | gnupg | 1.3.90 | Yes |
| Application | gnupg | gnupg | 1.3.91 | Yes |
| Application | gnupg | gnupg | 1.3.92 | Yes |
| Application | gnupg | gnupg | 1.3.93 | Yes |
| Application | gnupg | gnupg | 1.4 | Yes |
| Application | gnupg | gnupg | 1.4.0 | Yes |
| Application | gnupg | gnupg | 1.4.2 | Yes |
| Application | gnupg | gnupg | 1.4.3 | Yes |
| Application | gnupg | gnupg | 1.4.4 | Yes |
| Application | gnupg | gnupg | 1.4.5 | Yes |
| Application | gnupg | gnupg | 1.4.6 | Yes |
| Application | gnupg | gnupg | 1.4.8 | Yes |
| Application | gnupg | gnupg | 1.4.10 | Yes |
| Application | gnupg | gnupg | 1.4.11 | Yes |
| Application | gnupg | gnupg | 1.4.12 | Yes |
| Application | gnupg | gnupg | 1.4.13 | Yes |
| Application | gnupg | gnupg | 1.4.14 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For gnupg's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.