CVE-2007-3375 json
Stack-based buffer overflow in Lhaca File Archiver before 1.21 allows user-assisted remote attackers to execute arbitrary code via a crafte…
published 2007-06-25 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-3365
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.7%
- EPSS 4.7% chance of exploitation in 30 days, percentile 91%
- public exploits
- 0
- none known
Summary
Stack-based buffer overflow in Lhaca File Archiver before 1.21 allows user-assisted remote attackers to execute arbitrary code via a crafted LZH archive, as exploited by malware such as Trojan.Lhdropper.
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-2007-3375 updated
lhaca issue might affect lha packages
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
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
4.70% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
secunia.com
/advisories/25826
third-party-advisory, vendor-advisory
- symantec.com /enterprise/security_response/weblog/2007/06/beware_of_lzh.html
-
kb.cert.org
/vuls/id/871497
third-party-advisory, us-government-resource
- symantec.com /security_response/writeup.jsp?docid=2007-062506-5500-99&tabid=1
-
exchange.xforce.ibmcloud.com
/vulnerabilities/35116
vdb-entry
- vuln.sg /lhaca121-en.html
-
securityfocus.com
/bid/24604
vdb-entry
Sources
- CVE List CVE-2007-3375
- NVD CVE-2007-3375
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.