CVE-2007-0264
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 Winzip32.exe in WinZip 9.0 allows local users to cause a denial of service (application crash) and possibly execute arbitrary code via a long command line argument. NOTE: this issue may cross privilege boundaries if an application automatically invokes Winzip32.exe for untrusted input filenames, as in the case of a file upload application. NOTE: The provenance of this information is unknown; the details are obtained solely from third party information.
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 · moderate confidenceBuffer overflow in Winzip32.exe in WinZip 9.0 allows arbitrary command line arguments to overflow the buffer, causing denial of service (application crash) and potentially enabling arbitrary code execution. The vulnerability can be triggered locally via long command line arguments, and may cross privilege boundaries if untrusted filenames are automatically passed to Winzip32.exe by other applications (e.g., file upload handlers).
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= 9.0CVSS 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
- Local
- Complexity
- M
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:M/Au:S/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.
-
Locate Winzip32.exeSearch for Winzip32.exe in typical installation directories such as C:\Program Files\WinZip\ or C:\Program Files (x86)\WinZip\, or use the search feature in Windows Explorer.Affected if The file exists and belongs to WinZip 9.0
-
Check the file version of Winzip32.exeRight-click on Winzip32.exe, select Properties, then go to the Details tab and read the File Version field. Alternatively, use a command prompt: right-click the .exe file, select Create Shortcut, then open command prompt and type "shortcut.exe -dump" or use a tool like sigcheck or powershell (Get-ItemProperty).Affected if The file version shows exactly 9.0 or 9.0.0 (build 1024 or similar)
-
Check WinZip version via registryOpen Registry Editor (regedit) and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\WinZip or HKEY_CURRENT_USER\SOFTWARE\WinZip. Look for a value named "Version" or "VersionNum".Affected if The registry version value is 9.0 or 9.0.0
-
Verify the exact version stringIf WinZip is installed, you can also run WinZip and check Help > About WinZip, or run Winzip32.exe /? to see if version information is displayed.Affected if The displayed version is exactly 9.0 (not 8.x, 10.x, or higher)
You are affected if WinZip is installed and the version of Winzip32.exe is exactly 9.0 (or 9.0.0).
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 WinZip 9.0 to a patched version (current version). For applications that invoke WinZip, implement strict input validation on filenames/arguments before passing them to Winzip32.exe to prevent untrusted input from triggering the overflow.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0264 — 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-2007-0264 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