| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Lhaz 1.31. Affected by this vulnerability is an unknown functionality of the component Error Message Handler. Performing a manipulation results in stack-based overflow. This vulnerability is cataloged as CVE-2006-4116. There is no exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability classified as critical has been found in Lhaz 1.31. This affects some unknown processing of the component Error Message Handler. The manipulation with an unknown input leads to a stack-based overflow vulnerability. CWE is classifying the issue as CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Multiple stack-based buffer overflows in Lhaz before 1.32 allow user-assisted attackers to execute arbitrary code via a long filename in (1) an LHZ archive, when saving the filename during extraction; and (2) an LHZ archive with an invalid CRC checksum, when constructing an error message.
The weakness was shared 08/14/2006 by Tan Chew Keong (Website). It is possible to read the advisory at securityfocus.com. This vulnerability is uniquely identified as CVE-2006-4116 since 08/14/2006. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available.
It is declared as proof-of-concept.
Upgrading to version 1.32 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (28283), SecurityFocus (BID 19377†) and Secunia (SA21348†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.4
VulDB Base Score: 7.3
VulDB Temp Score: 6.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Stack-based overflowCWE: CWE-121 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Lhaz 1.32
Timeline
07/31/2006 🔍08/07/2006 🔍
08/14/2006 🔍
08/14/2006 🔍
08/14/2006 🔍
03/12/2015 🔍
08/02/2018 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Tan Chew Keong
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2006-4116 (🔍)
GCVE (CVE): GCVE-0-2006-4116
GCVE (VulDB): GCVE-100-31779
X-Force: 28283 - Lhaz LZH error message buffer overflow
SecurityFocus: 19377 - LHAZ LHA Long Multiple Buffer Overflow Vulnerabilities
Secunia: 21348 - Lhaz LZH File Handling Buffer Overflow Vulnerabilities, Moderately Critical
Vupen: ADV-2006-3173
Entry
Created: 03/12/2015 15:51Updated: 08/02/2018 09:02
Changes: 03/12/2015 15:51 (52), 08/02/2018 09:02 (9)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.