Tsugio Okamoto Lha vulnerabilities

CVE-2004-0771 [CRITICAL] CVE-2004-0771: Buffer overflow in the extract_one function from lhext.c in LHA may allow attackers to execute arbit Buffer overflow in the extract_one function from lhext.c in LHA may allow attackers to execute arbitrary code via a long w (working directory) command line option, a different issue than CVE-2004-0769. NOTE: this issue may be REJECTED if there are not any cases in which LHA is setuid or is otherwise used across security boundaries.

CVE-2004-0234 [CRITICAL] CWE-119 CVE-2004-0234: Multiple stack-based buffer overflows in the get_header function in header.c for LHA 1.14, as used i 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.

CVE-2004-0745 [CRITICAL] CVE-2004-0745: LHA 1.14 and earlier allows attackers to execute arbitrary commands via a directory with shell metac LHA 1.14 and earlier allows attackers to execute arbitrary commands via a directory with shell metacharacters in its name.

CVE-2004-0694 [MEDIUM] CWE-119 CVE-2004-0694: Buffer overflow in LHA 1.14 and earlier allows remote attackers to cause a denial of service (crash) Buffer overflow in LHA 1.14 and earlier allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via unknown vectors related to "command line processing," a different vulnerability than CVE-2004-0771. NOTE: this issue may be REJECTED if there are not any cases in which LHA is setuid or is otherwise used across s

CVE-2004-0235 [MEDIUM] CVE-2004-0235: Multiple directory traversal vulnerabilities in LHA 1.14 allow remote attackers or local users to cr Multiple directory traversal vulnerabilities in LHA 1.14 allow remote attackers or local users to create arbitrary files via an LHA archive containing filenames with (1) .. sequences or (2) absolute pathnames with double leading slashes ("//absolute/path").