CVE-2010-1898
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 · uneditedThe Common Language Runtime (CLR) in Microsoft .NET Framework 2.0 SP1, 2.0 SP2, 3.5, 3.5 SP1, and 3.5.1, and Microsoft Silverlight 2 and 3 before 3.0.50611.0 on Windows and before 3.0.41130.0 on Mac OS X, does not properly handle interfaces and delegations to virtual methods, which allows remote attackers to execute arbitrary code via (1) a crafted XAML browser application (aka XBAP), (2) a crafted ASP.NET application, or (3) a crafted .NET Framework application, aka "Microsoft Silverlight and Microsoft .NET Framework CLR Virtual Method Delegate 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 confidenceThe CLR in Microsoft .NET Framework 2.0 SP1-SP2, 3.5, 3.5 SP1, 3.5.1 and Silverlight 2/3 fails to properly handle interfaces and delegations to virtual methods, allowing remote attackers to execute arbitrary code through crafted XBAP, ASP.NET, or .NET applications.
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= 2.0= 3.5= 3.5.1<= 3.0.40818.0= 2.0.31005.00= 2.0.40115.00= 3.0.40624.00= 3.0.40723.0<= 3.0.50106.0= 3.0.40818.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
- 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.
-
Identify installed .NET Framework versionCheck the Windows registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v2.0.50727 (or v3.5 for .NET 3.5/3.5.1) for the Version value, or run 'clrver.exe' from the .NET Framework SDK if availableAffected if The installed version is 2.0.x, 3.5.x, or 3.5.1.x without the KB983583 or KB983582 security update applied
-
Identify installed Silverlight versionCheck the Windows registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Silverlight\Version (or on Mac, check /Library/Application Support/Microsoft/Silverlight/Player.txt), or run 'silverlight.exe -version' if installedAffected if The installed version is 3.0.40818.0, 2.0.31005.00, 2.0.40115.00, 3.0.40624.00, 3.0.40723.0, 3.0.50106.0 or any version prior to 3.0.50611.0 (Windows) or 3.0.41130.0 (Mac)
-
Determine if XBAP (XAML Browser Applications) are enabledIn Internet Explorer, check Internet Options > Security > Custom Level for the setting 'Enable XAML browser applications' (under .NET Framework components), or check the registry key HKLM\SOFTWARE\Microsoft\.NETFramework\xbapEnabledAffected if XBAP support is enabled and a user can be tricked into visiting a malicious website hosting a crafted XBAP
-
Check for exposed ASP.NET applicationsReview IIS or other web server configuration for any hosted ASP.NET applications that accept user input or deserialize data, and verify whether the .NET Framework version listed above is in use on those serversAffected if ASP.NET applications are running on an affected .NET Framework version and can accept untrusted input that could trigger the vulnerability
Your environment is affected if either .NET Framework version 2.0, 3.5, or 3.5.1 is installed without the security update, or Silverlight version 3.0.50106.0 or earlier is installed, particularly if XBAP or ASP.NET applications are exposed to untrusted input.
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.
dbcve · scopedApply Microsoft security updates KB983583 or KB983582 for .NET Framework and update Silverlight to version 3.0.50611.0 (Windows) or 3.0.41130.0 (Mac). Consider disabling XAML browser applications in Internet Explorer as a temporary workaround.
Silverlight 3.0.50611.0 (Windows) / 3.0.41130.0 (Mac) or .NET Framework 4.0; apply MS10-077 patch for .NET Framework 2.0/3.5
- 1. Identify the installed version of .NET Framework or Silverlight on affected systems using 'regedit' or the Windows Features/Programs and Features control panel.
- 2. For Silverlight on Windows: Uninstall the current Silverlight version and install version 3.0.50611.0 or later from the official Microsoft Silverlight download page.
- 3. For Silverlight on Mac OS X: Uninstall the current Silverlight version and install version 3.0.41130.0 or later from the official Microsoft Silverlight download page.
- 4. For .NET Framework: Apply Microsoft Security Bulletin MS10-077 or upgrade to .NET Framework 4.0, which includes the security fix.
- 5. Verify the update was successful by checking the installed version again.
- 6. Test affected applications (XBAP, ASP.NET, or .NET applications) to ensure functionality is maintained.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-1898 — 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-2010-1898 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