dbcve.org
Windows 7Operating system · Microsoft

CVE-2011-0660

HIGH · 9.3 CVSS v2.0 Published 2011-04-13
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 SMB client in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP1 and SP2, Windows Server 2008 Gold, SP2, R2, and R2 SP1, and Windows 7 Gold and SP1 allows remote SMB servers to execute arbitrary code via a crafted (1) SMBv1 or (2) SMBv2 response, aka "SMB Client Response Parsing 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

The SMB client in multiple Windows versions contains a parsing vulnerability in how it handles responses from SMB servers. A malicious SMB server can send crafted SMBv1 or SMBv2 responses that cause a buffer overflow, leading to arbitrary code execution on the connecting client.

MitigationApply Microsoft security updates MS11-019 and MS11-020 to affected Windows systems. Alternatively, block outbound SMB connections to untrusted servers at the network perimeter and disable SMBv1 if not required.

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 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 the installed Windows version
    Run 'winver' or 'systeminfo' from command prompt and note the Windows version and build number
    Affected if The version is Windows XP, Windows Vista, Windows 7, Windows Server 2003, or Windows Server 2008 (any edition)
  2. Confirm SMB client is enabled
    Check the SMB client service status: run 'sc query mup' or view SMB settings in Windows Features (SMB 1.0/CIFS File Sharing Client). For SMBv2, check registry key 'HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters' for 'SMB2' value
    Affected if SMB client (SMBv1 or SMBv2) is installed and enabled on the system
  3. Verify if security updates are applied
    Check for MS11-019 and MS11-020 updates: run 'wmic qfe list' or view 'View installed updates' in Control Panel, search for KB2490606 and KB2508429
    Affected if Neither MS11-019 (KB2490606) nor MS11-020 (KB2508429) security updates are installed

The system is affected if it runs an affected Windows version (XP, Vista, 7, Server 2003, Server 2008), has SMB client enabled, and is missing both MS11-019 and MS11-020 security updates.

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 Microsoft security updates MS11-019 and MS11-020 to affected Windows systems. Alternatively, block outbound SMB connections to untrusted servers at the network perimeter and disable SMBv1 if not required.

Recommended fix High confidence

Windows 10 or Windows 11 for desktop systems; Windows Server 2016 or later for server systems

  1. 1. Identify all systems running the affected Windows versions (Windows XP, Windows 2003 Server, Windows Vista, Windows Server 2008, Windows 7).
  2. 2. For Windows Vista, Windows Server 2008, and Windows 7 systems, apply Microsoft Security Bulletin MS11-019 (https://docs.microsoft.com/en-us/security-updates/securitybulletins/2011/ms11-019) which contains the patch for CVE-2011-0660.
  3. 3. Verify the patch is successfully installed by checking for the updated SMB client components.
  4. 4. For Windows XP and Windows 2003 Server systems that are end-of-life and no longer receive security updates, upgrade to a supported Windows version such as Windows 10 or Windows Server 2016/2019.
  5. 5. If upgrading is not immediately possible, implement network-level mitigations: block SMB traffic (ports 139, 445) at the perimeter firewall from untrusted networks, and disable SMBv1 client via registry setting: Set HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\SMB1 = 0 (DWORD).
  6. 6. After applying patches or mitigations, verify SMB client behavior is normal and the vulnerability is addressed.
Caveat Windows XP and 2003 Server are end-of-life and require full OS upgrade rather than patching; disabling SMBv1 may affect legacy applications that depend on SMBv1

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-2011-0660 — 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-2011-0660 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