CVE-2010-2434
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBuffer overflow in Arcext.dll 2.16.1 and earlier in pon software Explzh 5.62 and earlier allows remote attackers to execute arbitrary code via an LZH LHA file with a crafted header that is not properly handled during expansion.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceBuffer overflow in Arcext.dll versions 2.16.1 and earlier allows remote code execution when Explzh processes malicious LZH/LHA archive files. The vulnerability stems from improper handling of crafted archive headers during file expansion, causing a buffer overflow that can be leveraged by attackers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 5.62CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Explzh is installedLook for Explzh in the program files directory (typically C:\Program Files\Explzh or C:\Program Files (x86)\Explzh) or check the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an Explzh entryAffected if Explzh is not found on the system, the vulnerability does not apply
-
Determine installed Explzh versionRight-click on explzh.exe, select Properties, and check the Version tab. Alternatively, run 'explzh.exe /?' or check the registry key for the DisplayVersion valueAffected if The installed version is 5.62 or earlier, making it potentially vulnerable
-
Check Arcext.dll versionNavigate to the Explzh installation folder, right-click on Arcext.dll, select Properties, and check the File Version on the Details tabAffected if The Arcext.dll file version is 2.16.1 or earlier, indicating the vulnerable DLL is present
-
Verify LZH/LHA file handling is enabledOpen Explzh, go to Options or Settings, and check if LZH/LHA file extension associations or extraction features are enabled. You can also check if .lzh or .lha file types are registered with Explzh in the Windows file type associationsAffected if LZH/LHA file handling is enabled and associated with Explzh, creating the attack vector
-
Inspect recent LZH/LHA file activityCheck the Explzh application logs (if logging is enabled) or review recently opened .lzh/.lha files in the Windows recent documents folderAffected if Explzh has recently processed LZH/LHA files from untrusted or unknown sources, increasing exposure risk
The system is affected if Explzh version 5.62 or earlier with Arcext.dll version 2.16.1 or earlier is installed and LZH/LHA file handling is enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Explzh to a version newer than 5.62 that includes the patched Arcext.dll; avoid opening untrusted LZH/LHA files from unknown sources.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-2434 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2010-2434 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data