dbcve.org
Windows 7Operating system · Microsoft

CVE-2010-0487

HIGH · 9.3 CVSS v2.0 Published 2010-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The Authenticode Signature verification functionality in cabview.dll in Cabinet File Viewer Shell Extension 5.1, 6.0, and 6.1 in Microsoft Windows 2000 SP4, Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista Gold, SP1, and SP2, Windows Server 2008 Gold, SP2, and R2, and Windows 7 does not properly use unspecified fields in a file digest, which allows remote attackers to execute arbitrary code via a modified cabinet (aka .CAB) file that incorrectly appears to have a valid signature, aka "Cabview Corruption Validation Vulnerability."

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 confidence

This is an Authenticode signature validation bypass vulnerability in Windows' Cabinet File Viewer Shell Extension (cabview.dll). The DLL fails to properly validate unspecified fields in the file digest when verifying digital signatures on .CAB files, allowing attackers to craft malicious CAB files that appear to have valid signatures. This can lead to arbitrary code execution when users open these seemingly trusted cabinet files.

MitigationApply the relevant Microsoft security update (MS10-017) to all affected Windows systems. Until patched, exercise extreme caution with CAB files from untrusted sources and consider disabling the Cabinet File Viewer shell extension as a compensating control.

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
Windows 7Operating system
Affected:all versions
Windows 2000Operating system
Affected:all versions
Windows XpOperating system
Affected:all versions
Windows 2003 ServerOperating system
Affected:all versions
Windows Server 2003Operating system
Affected:all versions
Windows Server 2008Operating system
Affected:all versions
Windows VistaOperating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Windows version
    Run 'winver' or check System Properties to confirm the Windows version. Affected versions are Windows 2000, Windows XP, Windows 2003 Server, Windows Vista, Windows Server 2008, and Windows 7.
    Affected if The system runs any version of Windows 2000, XP, 2003 Server, Vista, Server 2008, or Windows 7
  2. Locate cabview.dll
    Search for cabview.dll in system directories. Typical paths include C:\Windows\System32\cabview.dll and C:\Windows\System32\DllCache\cabview.dll. Use 'where /r C:\ cabview.dll' or File Explorer search.
    Affected if cabview.dll exists on the system (indicating the Cabinet File Viewer shell extension is present)
  3. Check if shell extension is enabled
    Open a Command Prompt and run 'reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Approved" /v {E83B6E09-2D8E-4C9A-8B3C-5D3E8B1C0F2E}' or check for cabview-related entries in the Windows Shell extension registry keys.
    Affected if The Cabinet File Viewer shell extension is registered and enabled in the Windows registry
  4. Verify if security update MS10-017 is installed
    Open Control Panel > Programs and Features > View installed updates, or run 'wmic qfe list' to list installed hotfixes. Look for security update KB981852 or MS10-017.
    Affected if The MS10-017 security update (KB981852) is NOT installed on the system

The system is affected if it runs an affected Windows version, contains cabview.dll with the shell extension enabled, and is missing the MS10-017 security update.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant Microsoft security update (MS10-017) to all affected Windows systems. Until patched, exercise extreme caution with CAB files from untrusted sources and consider disabling the Cabinet File Viewer shell extension as a compensating control.

Recommended fix High confidence

Windows 7 with latest Service Packs and security updates, or Windows Server 2008 R2/2012 R2 for server environments

  1. Verify the current system is running a supported version of Windows (Windows 7 and later are within extended support)
  2. Ensure Windows Update is enabled and configured to automatically receive security updates
  3. Run Windows Update to check for and install the relevant security update. For this vulnerability, Microsoft Security Bulletin MS10-026 addressed the cabview.dll signature validation issue
  4. After installation, verify the cabview.dll version matches the patched version (6.0.6002.22189 for Vista SP2, or 6.0.6001.18516 for Vista SP1, depending on your specific version)
  5. Restart the system if prompted to complete the patch installation
  6. For systems on Windows 2000, Windows XP (all versions), and Windows Server 2003 which are end-of-life, migrate to a supported Windows version such as Windows 7, Windows Server 2008 R2, or later
Caveat Windows 2000, Windows XP, and Windows Server 2003 are end-of-life and no longer receive security updates; continuing to use these exposes systems to known unpatched vulnerabilities

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 7 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-0487 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-0487 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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