CVE-2013-4576
Last modified
CVE-2013-4576 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.45% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Gnupg | Gnupg | <= 1.4.15 |
| Gnupg | Gnupg | 1.0.0 |
| Gnupg | Gnupg | 1.0.1 |
| Gnupg | Gnupg | 1.0.2 |
| Gnupg | Gnupg | 1.0.3 |
| Gnupg | Gnupg | 1.0.4 |
| Gnupg | Gnupg | 1.0.5 |
| Gnupg | Gnupg | 1.0.6 |
| Gnupg | Gnupg | 1.0.7 |
| Gnupg | Gnupg | 1.2.0 |
| Gnupg | Gnupg | 1.2.1 |
| Gnupg | Gnupg | 1.2.2 |
| Gnupg | Gnupg | 1.2.3 |
| Gnupg | Gnupg | 1.2.4 |
| Gnupg | Gnupg | 1.2.5 |
| Gnupg | Gnupg | 1.2.6 |
| Gnupg | Gnupg | 1.2.7 |
| Gnupg | Gnupg | 1.3.0 |
| Gnupg | Gnupg | 1.3.1 |
| Gnupg | Gnupg | 1.3.2 |
| Gnupg | Gnupg | 1.3.3 |
| Gnupg | Gnupg | 1.3.4 |
| Gnupg | Gnupg | 1.3.6 |
| Gnupg | Gnupg | 1.3.90 |
| Gnupg | Gnupg | 1.3.91 |
| Gnupg | Gnupg | 1.3.92 |
| Gnupg | Gnupg | 1.3.93 |
| Gnupg | Gnupg | 1.4 |
| Gnupg | Gnupg | 1.4.0 |
| Gnupg | Gnupg | 1.4.2 |
| Gnupg | Gnupg | 1.4.3 |
| Gnupg | Gnupg | 1.4.4 |
| Gnupg | Gnupg | 1.4.5 |
| Gnupg | Gnupg | 1.4.6 |
| Gnupg | Gnupg | 1.4.8 |
| Gnupg | Gnupg | 1.4.10 |
| Gnupg | Gnupg | 1.4.11 |
| Gnupg | Gnupg | 1.4.12 |
| Gnupg | Gnupg | 1.4.13 |
| Gnupg | Gnupg | 1.4.14 |
References
- http://lists.gnupg.org/pipermail/gnupg-devel/2013-December/028102.htmlPatch, Vendor Advisory
- http://lists.gnupg.org/pipermail/gnupg-devel/2013-December/028102.htmlPatch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2013-4576?
How severe is CVE-2013-4576?
How do I fix CVE-2013-4576?
Are you affected by CVE-2013-4576?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
