{"id":"CVE-2004-0769","published":"2004-08-04T04:00:00Z","modified":"2024-08-08T00:31:46Z","title":"Buffer overflow in LHA allows remote attackers to execute arbitrary code via long pathnames in LHarc format 2 headers…","vendor":null,"product":null,"tier":"tail","description":{"text":"Buffer overflow in LHA allows remote attackers to execute arbitrary code via long pathnames in LHarc format 2 headers for a .LHZ archive, as originally demonstrated using the \"x\" option but also exploitable through \"l\" and \"v\", and fixed in header.c, a different issue than CVE-2004-0771.","provenance":"source","from":"CVE.org"},"cvss":null,"epss":{"score":0.09145,"percentile":0.95436,"provenance":"source"},"cwes":[],"references":[{"url":"http://www.redhat.com/support/errata/RHSA-2004-323.html","tags":["vendor-advisory","x_refsource_REDHAT"]},{"url":"https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11047","tags":["vdb-entry","signature","x_refsource_OVAL"]},{"url":"https://bugzilla.fedora.us/show_bug.cgi?id=1833","tags":["vendor-advisory","x_refsource_FEDORA"]},{"url":"https://exchange.xforce.ibmcloud.com/vulnerabilities/16917","tags":["vdb-entry","x_refsource_XF"]},{"url":"http://bugs.gentoo.org/show_bug.cgi?id=51285","tags":["x_refsource_CONFIRM"]},{"url":"http://www.gentoo.org/security/en/glsa/glsa-200409-13.xml","tags":["vendor-advisory","x_refsource_GENTOO"]},{"url":"http://lw.ftw.zamosc.pl/lha-exploit.txt","tags":["x_refsource_MISC"]},{"url":"http://marc.info/?l=bugtraq&m=108745217504379&w=2","tags":["mailing-list","x_refsource_BUGTRAQ"]},{"url":"http://www.redhat.com/support/errata/RHSA-2004-440.html","tags":["vendor-advisory","x_refsource_REDHAT"]}],"priority":{"score":19.1,"factors":[{"name":"EPSS percentile","points":19.09}]},"summary":{"text":"The flaw is a buffer overflow in LHA, the archive utility, in how it handles long pathnames within LHarc format 2 headers for .LHZ archives. The conditions are that an attacker supplies a crafted archive for the victim to process, with the \"x\" option demonstrated originally and the \"l\" and \"v\" options also able to trigger it, so the outcome is arbitrary code execution.","provenance":"ai","model":"claude-haiku-5-5","generatedAt":"2026-11-20T20:57:47Z"},"euvd":{"id":"EUVD-2004-0767","exploited":false,"provenance":"source"}}