Skip to content
Noroxi
CVE-2013-4576· NVD / CVE Program· CNA redhat

GnuPG 1.x before 1.4.16 generates RSA keys using sequences of introductions with certain patterns that introduce a side channel, which allow

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.

LowCVSS 2.1 · v2.0—No exploit Fix available
Published
Dec 20, 2013
Updated
Jun 16, 2026
EPSS
0.5% · 37th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

8

Monitor

Low priority for now.

CVSS
8 / 40 · 2.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

Affected systems

VendorProduct
gnupggnupg

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • gnupg gnupgup to 1.4.15 inclusive
  • gnupg gnupg1.0.0
  • gnupg gnupg1.0.1
  • gnupg gnupg1.0.2
  • gnupg gnupg1.0.3
  • gnupg gnupg1.0.4
  • gnupg gnupg1.0.5
  • gnupg gnupg1.0.6
  • gnupg gnupg1.0.7
  • gnupg gnupg1.2.0
  • gnupg gnupg1.2.1
  • gnupg gnupg1.2.2
  • gnupg gnupg1.2.3
  • gnupg gnupg1.2.4
  • gnupg gnupg1.2.5
  • gnupg gnupg1.2.6
  • gnupg gnupg1.2.7
  • gnupg gnupg1.3.0
  • gnupg gnupg1.3.1
  • gnupg gnupg1.3.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:6.0gnupgbefore 1.4.10-4+squeeze41.4.10-4+squeeze4
Debian:7gnupgbefore 1.4.12-7+deb7u31.4.12-7+deb7u3
Red Hat:enterprise_linux:5::clientgnupgbefore 0:1.4.5-18.el5_10.10:1.4.5-18.el5_10.1
Red Hat:enterprise_linux:5::clientgnupg-debuginfobefore 0:1.4.5-18.el5_10.10:1.4.5-18.el5_10.1

Other highest-scoring records for the same primary product.

  • CVE-2026-24881In GnuPG before 2.5.17, a crafted CMS (S/MIME) EnvelopedData message carrying an oversized wrapped session key can cause a stack-based buffe
    40Plan
  • CVE-2008-1530GnuPG (gpg) 1.4.8 and 2.0.8 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via crafted dup
    38Monitor
  • CVE-2018-1000858GnuPG version 2.1.12 - 2.2.11 contains a Cross ite Request Forgery (CSRF) vulnerability in dirmngr that can result in Attacker controlled CS
    35Monitor
  • CVE-2010-2547Use-after-free vulnerability in kbx/keybox-blob.c in GPGSM in GnuPG 2.x through 2.0.16 allows remote attackers to cause a denial of service
    34Monitor
  • CVE-2018-12020mainproc.c in GnuPG before 2.2.8 mishandles the original filename during decryption and verification actions, which allows remote attackers
    33Monitor
  • CVE-2026-24882In GnuPG before 2.5.17, a stack-based buffer overflow exists in tpm2daemon during handling of the PKDECRYPT command for TPM-backed RSA and E
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:gnupg1.4.10-4+squeeze4 · Debian:6.0Package registry (OSV)
red hat:gnupg0:1.4.5-18.el5_10.1 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:gnupg-debuginfo0:1.4.5-18.el5_10.1 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
P · data can be read
Integrity
none
Availability
none
Attack complexity
Low
Confidentiality impact
P
Integrity impact
None
Availability impact
None

CVSS vector

AV:L/AC:L/Au:N/C:P/I:N/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records