CVE-2006-6884
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 the WZFILEVIEW.FileViewCtrl.61 ActiveX control (aka Sky Software "FileView" ActiveX control) for WinZip 10.0 Build 6667 allows remote attackers to execute arbitrary code via a long argument to the CreateNewFolderFromName method, a different vulnerability than CVE-2006-5198.
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 the WZFILEVIEW.FileViewCtrl.61 ActiveX control (Sky Software FileView control bundled with WinZip 10.0 Build 6667). The CreateNewFolderFromName method fails to properly validate input length, allowing a long argument to overflow a buffer and execute arbitrary code remotely.
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= 10.0_build_6667CVSS 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 WinZip versionCheck the installed WinZip version via the executable (typically in Program Files\WinZip\winzip32.exe) or by querying the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\WinZip, looking for the DisplayVersion valueAffected if The installed version is WinZip 10.0_build_6667 exactly
-
Confirm ActiveX control registrationSearch the Windows registry for the CLSID of the WZFILEVIEW.FileViewCtrl.61 control under HKEY_CLASSES_ROOT\WZFILEVIEW.FileViewCtrl.61 or check for the component's ProgID registrationAffected if The WZFILEVIEW.FileViewCtrl.61 ActiveX control is registered on the system
-
Check if control is allowed in Internet ExplorerInspect Internet Explorer security settings or group policy for ActiveX control permissions. This can be found in IE zone settings (Internet Options > Security > Custom Level) or via registry under HKLM\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\DomainsAffected if The WZFILEVIEW.FileViewCtrl.61 ActiveX control is permitted to load in any browser zone (particularly Internet or Intranet zones)
-
Identify the vulnerable method presenceVerify the presence of the FileView control DLL or ActiveX component files (such as wzFileView.dll or similar) in the WinZip installation directory that implements the CreateNewFolderFromName methodAffected if The FileView control component containing the CreateNewFolderFromName method is present on the system
A user is affected if WinZip 10.0_build_6667 is installed AND the WZFILEVIEW.FileViewCtrl.61 ActiveX control is registered and permitted to run in browser contexts.
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 to a version that includes the patched ActiveX control, or disable the WZFILEVIEW.FileViewCtrl.61 ActiveX control through browser security settings or group policy to block instantiation.
- Consultation2.0 h
- Implementation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-6884 — 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-2006-6884 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