CVE-2011-1336
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 ALZip 8.21 and earlier allows remote attackers to execute arbitrary code via a crafted mim file.
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 vulnerability in ALZip versions 8.21 and earlier allows remote code execution when processing a specially crafted .mim file. The vulnerability stems from insufficient bounds checking when parsing the .mim file format, leading to heap or stack buffer overflow that can be exploited to execute arbitrary code.
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<= 8.21= 8.0= 8.12CVSS 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.
-
Verify ALZip is installedCheck for ALZip installation: Look for 'ALZip' in the list of installed programs (Windows Control Panel > Programs and Features), or search for the executable file 'ALZip.exe' in Program Files folders (typically C:\Program Files\ESTsoft\ALZip or C:\Program Files (x86)\ESTsoft\ALZip)Affected if ALZip is found installed on the system
-
Determine installed ALZip versionRight-click on ALZip.exe, select Properties, then go to the Details tab to view the File Version. Alternatively, open ALZip, go to Help > About ALZip to see the version numberAffected if The displayed version is 8.21, 8.12, 8.0, or any version number equal to or lower than 8.21
-
Confirm .mim file association or ALZip as default handlerRight-click any .mim file (or create a test .mim file), select Properties, then open with > choose default program, and verify ALZip is listed as an option or as the default handler for .mim filesAffected if ALZip is associated as the default program or an option for opening .mim files
-
Check for vulnerable ALZip processOpen Task Manager, look for ALZip.exe running as a process, or attempt to open a .mim file with ALZip to trigger the parsing code pathAffected if ALZip is running or can be invoked to process .mim files
The system is affected if ALZip version 8.21 or earlier is installed and is configured to handle .mim files, as the buffer overflow vulnerability is triggered during .mim file parsing.
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 dataUpgrade ALZip to a version newer than 8.21 that includes the security patch. Until patched, avoid opening .mim files from untrusted sources.
- Consultation3.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 $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-1336 — 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-2011-1336 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