Lha vulnerabilitiesRanked by how likely they are to be used.
Lha is made by Tsugio Okamoto. We track 5 published vulnerabilities in it, across 3 versions. None of them is on the list of flaws known to be exploited today. If you run Lha, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Lha vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Lha's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Lha flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 19%CVE-2004-0771Critical
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.
- 10%CVE-2004-0234Critical
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...
- 4.1%CVE-2004-0235Medium
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) ..
- 3.1%CVE-2004-0745Critical
LHA 1.14 and earlier allows attackers to execute arbitrary commands via a directory with shell metacharacters in its name.
- 2.5%CVE-2004-0694Medium
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...
Running Lha? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Lha on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 5 published vulnerabilities listed under the name Lha, across 3 versions.
None of Lha's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Lha. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.