Skip to content
Fencer Intel
medium 5.0

CVE-2014-4617 json

The do_uncompress function in g10/compress.c in GnuPG 1.x before 1.4.17 and 2.x before 2.0.24 allows context-dependent attackers to cause a…

published 2014-06-25 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-4543

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.3%
EPSS 3.3% chance of exploitation in 30 days, percentile 88%
public exploits
0
none known

Summary

The do_uncompress function in g10/compress.c in GnuPG 1.x before 1.4.17 and 2.x before 2.0.24 allows context-dependent attackers to cause a denial of service (infinite loop) via malformed compressed packets, as demonstrated by an a3 01 5b ff byte sequence.

Patch / fix

  • gnupg2 Debian 14, Debian 13, Debian 12 2.0.24-1

debian advisories DEBIAN-CVE-2014-4617

  • gnupg Ubuntu 14.04 LTS 1.4.16-1ubuntu2.1
  • gnupg2 Ubuntu 14.04 LTS 2.0.22-3ubuntu1.1

ubuntu advisories UBUNTU-CVE-2014-4617

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • gpg2 openSUSE Tumbleweed 2.1.16-1.1

opensuse advisories openSUSE-SU-2024:10102-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-4617 updated cvss 5.0

gnupg: infinite loop when decompressing data packets

  • Red Hat Enterprise Linux 5 gnupg, gnupg2 Red Hat Enterprise Linux 6 gnupg2, gnupg2-smime Red Hat Enterprise Linux 7 gnupg2, gnupg2-smime
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.31% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.