dbcve.org
.net FrameworkApplication · Microsoft

CVE-2013-3132

HIGH · 9.3 CVSS v2.0 Published 2013-07-10
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 1.0 SP3, 1.1 SP1, 2.0 SP2, 3.5, 3.5.1, 4, and 4.5 does not properly check the permissions of objects that use reflection, which allows remote attackers to execute arbitrary code via (1) a crafted XAML browser application (XBAP) or (2) a crafted .NET Framework application, aka "Delegate Reflection Bypass 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 a privilege escalation vulnerability in Microsoft .NET Framework's reflection API. The vulnerability allows malicious code to bypass permission checks when invoking delegates through reflection, enabling arbitrary code execution. Attackers can exploit this by tricking users into running crafted XBAP (XAML Browser Applications) or standalone .NET Framework applications that abuse the delegate reflection mechanism to circumvent Code Access Security (CAS) restrictions.

MitigationApply Microsoft security update MS13-052 (or subsequent cumulative updates) to all affected .NET Framework installations. For web applications, consider disabling XBAP in Internet Explorer and restricting .NET code execution policies where possible until patches are 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:= 1.0= 1.1= 2.0= 3.5= 3.5.1= 4.0= 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. Identify installed .NET Framework version
    Check the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v{version}\Release for .NET Framework 4.x, or HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v{version}\Version for older versions. Use 'wmic product list' or check Programs and Features to list installed Microsoft .NET Framework versions.
    Affected if The installed version matches 1.0, 1.1, 2.0, 3.5, 3.5.1, 4.0, or 4.5 (without the MS13-052 security update applied).
  2. Confirm if security update MS13-052 is applied
    Check Windows Update history or the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\* for update package 'MS13-052' or KB2840628 (for .NET 4.0/4.5) and KB2840629 (for .NET 2.0/3.5). Alternatively, run 'Get-Hotfix -Id KB2840628' or 'Get-Hotfix -Id KB2840629' in PowerShell if available.
    Affected if The security update MS13-052 (KB2840628 or KB2840629) is NOT installed on the system.
  3. Determine if XBAP execution is enabled
    Check Internet Explorer security settings: go to Internet Options > Security > Custom Level > Enable XAML browser applications (XBAP). Also check if the feature is disabled via Group Policy under Computer Configuration > Administrative Templates > Windows Components > Internet Explorer > Turn off XBAP support.
    Affected if XBAP is enabled in Internet Explorer or allowed by policy, allowing malicious XBAP to load and exploit the vulnerability.
  4. Assess if code execution policies permit untrusted code
    Review the .NET Framework Code Access Security (CAS) policy using 'caspol -list' or check registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion for CAS settings. Determine if 'Everything' or 'SkipVerification' permissions are granted to zones other than LocalIntranet or MyComputer.
    Affected if CAS policies allow execution of partially trusted or untrusted code from network or Internet zones, enabling the reflection bypass.

A system is affected if it runs any of .NET Framework versions 1.0, 1.1, 2.0, 3.5, 3.5.1, 4.0, or 4.5 WITHOUT the MS13-052 security update AND allows execution of untrusted code or XBAP applications.

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 MS13-052 (or subsequent cumulative updates) to all affected .NET Framework installations. For web applications, consider disabling XBAP in Internet Explorer and restricting .NET code execution policies where possible until patches are deployed.

Recommended fix High confidence
  1. Check the installed .NET Framework version by reviewing registry keys under HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v[version]\SP
  2. Identify the specific version (1.0 SP3, 1.1 SP1, 2.0 SP2, or 3.5/3.5.1) installed on the system
  3. For .NET Framework 1.0 SP3 and 1.1 SP1: Apply security update KB2800277 from Microsoft Security Bulletin MS13-040
  4. For .NET Framework 2.0 SP2: Apply security update KB2833941 from Microsoft Security Bulletin MS13-052
  5. For .NET Framework 3.5 and 3.5.1: Apply security update KB2833941 from Microsoft Security Bulletin MS13-052
  6. After applying updates, restart the system and verify the updates are installed via Windows Update or Programs and Features
Caveat Patches for these legacy .NET Framework versions may require prior updates; ensure compatible service packs are installed. End-of-life versions 1.0 and 1.1 may not receive patches on newer Windows versions.

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

Fix this in .net Framework Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA4.0 h
40.0 hours of engineering $6,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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