# CVE-2013-4576: Information disclosure in n/a

> Physically proximate attackers can extract RSA keys from GnuPG via acoustic cryptanalysis during decryption, violating the developer's side-channel resistance policy.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Dec 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DSA-2821-1, GHSA-f43f-q929-x2qf, MGASA-2013-0382, RHSA-2014:0016

## What is CVE-2013-4576?

CVE-2013-4576 is a low-severity vulnerability in n/a, published on 20 Dec 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-255

## Which versions are affected by CVE-2013-4576?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gnupg` | Red Hat:enterprise_linux:5::client | All versions | 0:1.4.5-18.el5_10.1 |
| `gnupg-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:1.4.5-18.el5_10.1 |
| `gnupg` | Red Hat:enterprise_linux:5::server | All versions | 0:1.4.5-18.el5_10.1 |
| `gnupg-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:1.4.5-18.el5_10.1 |

Products: Gnupg Gnupg.

## How do I fix CVE-2013-4576?

Upgrade to a fixed version.

## Is CVE-2013-4576 being exploited?

There is no known exploitation of CVE-2013-4576 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-3515](https://insights.sbomify.com/CVE-2022-3515/): Integer overflow in libksba (critical 9.8)
- [CVE-2008-1530](https://insights.sbomify.com/CVE-2008-1530/): Memory corruption in n/a (critical 9.3)
- [CVE-2026-24882](https://insights.sbomify.com/CVE-2026-24882/): Memory corruption in GnuPG (high 8.4)
- [CVE-2026-24881](https://insights.sbomify.com/CVE-2026-24881/): Memory corruption in GnuPG (high 8.1)
- [CVE-2025-68973](https://insights.sbomify.com/CVE-2025-68973/): Memory corruption in GnuPG (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4576 and fix it if it is affected.

What it is: CVE-2013-4576 is a low-severity vulnerability in n/a, published on 20 Dec 2013. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-4576 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-2013-4576/ (Markdown: https://insights.sbomify.com/CVE-2013-4576/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-4576
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-4576
- OSV: https://osv.dev/vulnerability/CVE-2013-4576

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-4576/
Summaries are generated and may contain mistakes; the official description above is the record.