dbcve.org
.net FrameworkApplication · Microsoft

CVE-2011-0664

HIGH · 9.3 CVSS v2.0 Published 2011-06-16
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
Microsoft .NET Framework 2.0 SP1 and SP2, 3.5 Gold and SP1, 3.5.1, and 4.0, and Silverlight 4 before 4.0.60531.0, does not properly validate arguments to unspecified networking API functions, which allows remote attackers to execute arbitrary code via (1) a crafted XAML browser application (aka XBAP), (2) a crafted ASP.NET application, (3) a crafted .NET Framework application, or (4) a crafted Silverlight application, aka ".NET Framework Array Offset 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

A vulnerability in Microsoft .NET Framework and Silverlight exists due to improper validation of arguments (specifically array offsets) in unspecified networking API functions. Remote attackers can execute arbitrary code by tricking users into running crafted XBAP, ASP.NET, .NET Framework, or Silverlight applications that pass maliciously constructed input to these APIs.

MitigationApply Microsoft security update MS11-028 which addresses this vulnerability in all affected .NET Framework and Silverlight versions. As a defense-in-depth measure, disable or restrict XAML browser applications (XBAP) and Silverlight in browsers until patches can be deployed.

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
.net FrameworkApplication
Affected:= 4.0= 3.5.1= 2.0= 3.5
SilverlightApplication
Affected:= 4.0.60310.0

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. Check installed .NET Framework version
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full (for .NET 4.0) or HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5, v3.0, v2.0. Check the 'Version' value in each subkey. Alternatively, run 'dir %WINDIR%\Microsoft.NET\Framework\v*' in command prompt to list installed versions.
    Affected if The installed version matches exactly 2.0, 3.5, 3.5.1, or 4.0 without the MS11-028 security update applied.
  2. Check installed Silverlight version
    Open Control Panel > Programs and Features, or run 'reg query HKLM\SOFTWARE\Microsoft\Silverlight /v Version' in command prompt to retrieve the installed Silverlight version.
    Affected if The installed Silverlight version is 4.0.60310.0.
  3. Verify if MS11-028 security update is installed
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\UpdateExeVolatile or check 'View installed updates' in Control Panel for security update KB2487367 (.NET Framework) or KB2506172 (Silverlight). Alternatively, run 'wmic qfe list' to list installed hotfixes.
    Affected if Neither KB2487367 nor KB2506172 is listed among installed updates.
  4. Check if XBAP browser applications are enabled
    In Internet Explorer, go to Internet Options > Security > Custom Level and check the settings under 'XAML browser applications' or 'Loose XAML'. Check the registry path HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\XBAP for EnableEnhancedSecurity or similar settings.
    Affected if XBAP is set to Enabled or Prompt in browser security settings.

A system is affected if it has .NET Framework 2.0, 3.5, 3.5.1, or 4.0, or Silverlight 4.0.60310.0, AND the MS11-028 security updates (KB2487367 or KB2506172) are not installed.

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 update MS11-028 which addresses this vulnerability in all affected .NET Framework and Silverlight versions. As a defense-in-depth measure, disable or restrict XAML browser applications (XBAP) and Silverlight in browsers until patches can be deployed.

Recommended fix High confidence

Silverlight: upgrade to 4.0.60531.0 or later; .NET Framework: apply MS11-028 security update (April 2011)

  1. For Silverlight: Verify current version by checking Control Panel > Programs > Microsoft Silverlight
  2. Download and install Silverlight version 4.0.60531.0 or later from the official Microsoft Silverlight download page
  3. For .NET Framework: Apply Microsoft Security Bulletin MS11-028 (April 2011) which contains the fix for this vulnerability
  4. Ensure Windows Update is enabled and check for applicable security updates for Microsoft .NET Framework
  5. After installation, restart the affected system if prompted
  6. Verify the installed version matches the fixed release (Silverlight 4.0.60531.0 or later; .NET Framework patches from MS11-028)
Caveat Exercise caution in production environments - test patches in a staging environment before deployment to ensure compatibility with existing applications

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

Fix this in .net Framework Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-0664 — 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-0664 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