dbcve.org
.net FrameworkApplication · Microsoft

CVE-2013-0002

HIGH · 9.3 CVSS v2.0 Published 2013-01-09
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
Buffer overflow in the Windows Forms (aka WinForms) component in Microsoft .NET Framework 1.0 SP3, 1.1 SP1, 2.0 SP2, 3.0 SP2, 3.5, 3.5.1, 4, and 4.5 allows remote attackers to execute arbitrary code via (1) a crafted XAML browser application (XBAP) or (2) a crafted .NET Framework application that leverages improper counting of objects during a memory copy operation, aka "WinForms Buffer Overflow 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

Buffer overflow in Windows Forms (WinForms) component of Microsoft .NET Framework allows remote code execution through improper object counting during memory copy operations. Exploitable via crafted XBAP (XAML Browser Applications) or malicious .NET applications.

MitigationApply Microsoft security patches for all affected .NET Framework versions (1.0 SP3 through 4.5). Consider disabling XBAP in Internet Explorer as a defense-in-depth measure.

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:= 1.0= 1.1= 2.0= 4.0= 3.5= 3.5.1= 4.5

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. Determine installed .NET Framework version
    Check the Windows Registry for the .NET Framework version by running: 'reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" /v Version' for .NET 4.x or 'reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5" /v Version' for .NET 3.5. PowerShell can also be used: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full' -Name Version
    Affected if The installed version matches 1.0, 1.1, 2.0, 3.5, 3.5.1, 4.0, or 4.5 (or any version falling within these release families without the security patch applied)
  2. Verify if WinForms is in use
    Check if any .NET WinForms applications are installed or running on the system. Look for executables compiled against .NET in Program Files, or check running processes for applications using System.Windows.Forms. Inspect the Global Assembly Cache (GAC) at C:\Windows\assembly for Microsoft.Windows.Forms entries.
    Affected if WinForms components (System.Windows.Forms.dll) are present and loaded by .NET applications on the system
  3. Confirm XBAP support is enabled in Internet Explorer
    Check the Internet Explorer security settings for XAML Browser Applications. In IE, go to Internet Options > Security > Custom Level > Enable XAML Browser Applications. Alternatively, check the registry key: 'reg query "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\2" /v 2500' for zone settings, or examine IE add-on management for 'Windows Presentation Foundation' add-ons.
    Affected if XBAP support is enabled in Internet Explorer, allowing .NET code to run in the browser context
  4. Check for .NET application execution policy
    Review whether .NET applications can be executed on the system by checking file associations for .exe and .config files, and verify the presence of the .NET runtime. Run 'dir C:\Windows\Microsoft.NET\Framework' to list installed runtime versions.
    Affected if .NET Framework runtime is installed and .NET applications can be launched on the system

The environment is affected if a vulnerable .NET Framework version (1.0 through 4.5) is installed AND WinForms is in use OR XBAP support is enabled, allowing the buffer overflow to be triggered through malicious XBAP content or a crafted .NET application.

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 patches for all affected .NET Framework versions (1.0 SP3 through 4.5). Consider disabling XBAP in Internet Explorer as a defense-in-depth measure.

Recommended fix Moderate confidence

Migrate to .NET Framework 4.8 or transition to .NET 6/7/8 (LTS)

  1. This vulnerability affects .NET Framework versions that are all end-of-life and no longer supported by Microsoft.
  2. For .NET Framework 1.0 SP3, 1.1 SP1, 2.0 SP2, and 4.0: Microsoft no longer provides security updates as these versions reached end of support.
  3. There is no patch available for these end-of-life versions.
  4. Mitigation options: 1) Migrate applications to a supported .NET Framework version (4.8 or later) or .NET Core/.NET 5+; 2) Disable .NET Framework applications in browser settings; 3) Block XBAP and untrusted .NET applications at the network perimeter; 4) Apply network segmentation to isolate systems running these old .NET versions.
Caveat Full application migration testing required; older .NET Framework applications may require code changes to run on newer frameworks or .NET Core/.NET 5+

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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