dbcve.org
.net FrameworkApplication · Microsoft

CVE-2013-0004

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
Microsoft .NET Framework 1.0 SP3, 1.1 SP1, 2.0 SP2, 3.0 SP2, 3.5, 3.5.1, 4, and 4.5 does not properly validate the permissions of objects in memory, which allows remote attackers to execute arbitrary code via (1) a crafted XAML browser application (XBAP) or (2) a crafted .NET Framework application, aka "Double Construction 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 permission validation vulnerability in Microsoft .NET Framework where the framework improperly validates the permissions of objects in memory during construction. This allows remote attackers to bypass security restrictions and execute arbitrary code via specially crafted XBAP (XAML Browser Applications) or malicious .NET Framework applications.

MitigationApply Microsoft security updates for all affected .NET Framework versions (1.0 SP3 through 4.5) via Windows Update or manual patch deployment. Disable XAML browser applications (XBAP) in Internet Explorer and restrict .NET code execution policies whereXBAP and untrusted .NET applications are 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
.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. Identify installed .NET Framework version
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v\Full (or use 'reg query "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" /v Version' in command prompt)
    Affected if The installed version matches 1.0, 1.1, 2.0, 3.5, 3.5.1, 4.0, or 4.5
  2. Check for .NET Framework service pack level
    In the same registry path, check the 'SP' value ( DWORD ) to determine the Service Pack level installed
    Affected if The version is affected and SP level is below any applied Microsoft security update for this CVE (version and SP combination falls within unpatched ranges)
  3. Verify XBAP support status in Internet Explorer
    In Internet Explorer, go to Internet Options > Security > Custom Level > Enable .NET Framework XAML Browser Applications setting, or check registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\xbapEnable
    Affected if XBAP is enabled (set to 'Enable' or value 1) - this is the primary attack vector for this vulnerability
  4. Check .NET Framework configuration for code access security
    Review .NET Framework configuration files (machine.config or app.config) or use caspol.exe tool to inspect Code Access Security policy settings
    Affected if CAS policy allows execution of untrusted code or partial trust applications without proper restrictions

You are affected if your system runs any unpatched .NET Framework version (1.0 SP3 through 4.5) AND has XBAP enabled in Internet Explorer or permits untrusted .NET 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 updates for all affected .NET Framework versions (1.0 SP3 through 4.5) via Windows Update or manual patch deployment. Disable XAML browser applications (XBAP) in Internet Explorer and restrict .NET code execution policies whereXBAP and untrusted .NET applications are not required.

Recommended fix Moderate confidence

N/A - this is a patch/cumulative update situation, not a version upgrade

  1. Consult Microsoft Security Bulletin MS13-004 for the specific security update (KB article) corresponding to your installed .NET Framework version
  2. For .NET Framework 1.0 SP3 apply KB2742599
  3. For .NET Framework 1.1 SP1 apply KB2742597
  4. For .NET Framework 2.0 SP2 apply KB2742596
  5. For .NET Framework 3.0 SP2, 3.5, or 3.5.1 apply KB2756919
  6. For .NET Framework 4 apply KB2742595
  7. For .NET Framework 4.5 apply KB2742593
  8. Restart affected systems after applying updates
Caveat Testing in non-production environment recommended before deploying patches, especially for business-critical .NET 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
  • 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-0004 — 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-0004 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