dbcve.org
.net FrameworkApplication · Microsoft

CVE-2012-0163

HIGH · 9.3 CVSS v2.0 Published 2012-04-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 validate function parameters, 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 ".NET Framework Parameter Validation 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 parameter validation vulnerability in multiple versions of Microsoft .NET Framework (1.0 SP3 through 4.5) that allows remote attackers to execute arbitrary code via crafted XBAP applications, ASP.NET applications, or standalone .NET applications. The lack of proper validation of function parameters enables code execution without requiring authentication.

MitigationApply the Microsoft security updates released in April 2012 for this vulnerability (MS12-025). Prior to deployment, inventory all systems running affected .NET Framework versions and test critical applications post-patch to ensure compatibility.

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
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full (for .NET 4.0/4.5) or HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5 (for .NET 3.5/3.5.1) or HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v2.0 (for .NET 2.0) or HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v1.1 (for .NET 1.1) or HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v1.0 (for .NET 1.0). Check the Version value in each subkey to determine which versions are installed.
    Affected if The installed version matches any of these: 1.0, 1.1, 2.0, 3.5, 3.5.1, 4.0, or 4.5.
  2. Verify .NET Framework feature is in use
    Since this vulnerability affects any .NET application (XBAP, ASP.NET, or standalone), confirm that .NET Framework is actively installed and in use on the system by checking for .NET-related services, applications, or IIS applications pools configured for .NET.
    Affected if .NET Framework is installed and running applications.
  3. Check if XBAP applications are hosted
    Examine IIS or any web server configuration for hosted XBAP (XAML Browser Application) applications, or check if users have the ability to run XBAP content from web browsers.
    Affected if XBAP applications are hosted or users can load XBAP content from untrusted sources.

If the system has any of the affected .NET Framework versions (1.0, 1.1, 2.0, 3.5, 3.5.1, 4.0, or 4.5) installed and is running .NET applications, it is potentially affected by this parameter validation vulnerability.

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 the Microsoft security updates released in April 2012 for this vulnerability (MS12-025). Prior to deployment, inventory all systems running affected .NET Framework versions and test critical applications post-patch to ensure compatibility.

Recommended fix High confidence

Microsoft Security Update MS12-025 (or later cumulative updates)

  1. Locate and apply the Microsoft security update MS12-025, which addresses this vulnerability in the .NET Framework
  2. For .NET Framework 1.0 SP3: Apply security update KB2656378
  3. For .NET Framework 1.1 SP1: Apply security update KB2656374
  4. For .NET Framework 2.0 SP2: Apply security update KB2656352
  5. For .NET Framework 3.5: Apply security update KB2656354
  6. For .NET Framework 3.5.1: Apply security update KB2656355
  7. For .NET Framework 4: Apply security update KB2656351
  8. After applying updates, verify the patches were installed successfully via Windows Update or by checking installed updates
Caveat Patches for older unsupported .NET Framework versions may have compatibility issues with legacy applications; test thoroughly before production deployment

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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