Skip to content
Fencer Vulns
critical 10.0

CVE-2004-0234 in the critical feed json

Multiple stack-based buffer overflows in the get_header function in header.c for LHA 1.14, as used in products such as Barracuda Spam Firew…

published 2004-05-05 22 y ago modified 2026-06-16 4 mo ago also EUVD-2004-0234

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

Summary

Multiple stack-based buffer overflows in the get_header function in header.c for LHA 1.14, as used in products such as Barracuda Spam Firewall, allow remote attackers or local users to execute arbitrary code via long directory or file names in an LHA archive, which triggers the overflow when testing or extracting the archive.

Patch / fix

  • lha RHEL 3 1.14i-10.2

red hat advisories RHSA-2004:178

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-2004-0234 updated

security flaw

  • Red Hat Desktop version 3 lha 1.14i-10.2 Red Hat Enterprise Linux AS version 3 lha 1.14i-10.2 Red Hat Enterprise Linux ES version 3 lha 1.14i-10.2 Red Hat Enterprise Linux WS version 3 lha 1.14i-10.2
    fixed: vendor fix RHSA-2004:178
  • Red Hat Linux 9
    fixed: vendor fix RHSA-2004:179

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

10.26% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • securityfocus.com http://www.securityfocus.com/bid/10243 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

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.