Skip to content
Fencer Vulns
medium 5.0

CVE-2006-4338 json

unlzh.c in the LHZ component in gzip 1.3.5 allows context-dependent attackers to cause a denial of service (infinite loop) via a crafted GZ…

published 2006-09-19 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-4326

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

Summary

unlzh.c in the LHZ component in gzip 1.3.5 allows context-dependent attackers to cause a denial of service (infinite loop) via a crafted GZIP archive.

Patch / fix

  • gzip Debian 14, Debian 13, Debian 12 1.3.5-15

debian advisories DEBIAN-CVE-2006-4338

  • gzip RHEL 3 1.3.3-13.rhel3
  • gzip RHEL 4 1.3.3-16.rhel4

red hat advisories RHSA-2006:0667

  • timidity openSUSE Tumbleweed 2.14.0-3.10

opensuse advisories openSUSE-SU-2024:10440-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-2006-4338 updated

security flaw

  • Red Hat Desktop version 3 gzip 1.3.3-13.rhel3 Red Hat Enterprise Linux AS version 3 gzip 1.3.3-13.rhel3 Red Hat Enterprise Linux AS version 4 gzip 1.3.3-16.rhel4 Red Hat Enterprise Linux Desktop version 4 gzip 1.3.3-16.rhel4 Red Hat Enterprise Linux ES version 3 gzip 1.3.3-13.rhel3 Red Hat Enterprise Linux ES version 4 gzip 1.3.3-16.rhel4
    +2 more products
    Red Hat Enterprise Linux WS version 3 gzip 1.3.3-13.rhel3 Red Hat Enterprise Linux WS version 4 gzip 1.3.3-16.rhel4
    fixed: vendor fix RHSA-2006:0667

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.90% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

References

Sources

Fencer Vulns 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.