dbcve.org
.net FrameworkApplication · Microsoft

CVE-2013-0003

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 a System.DirectoryServices.Protocols (S.DS.P) namespace method in Microsoft .NET Framework 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 a missing array-size check during a memory copy operation, aka "S.DS.P 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 System.DirectoryServices.Protocols (S.DS.P) namespace in Microsoft .NET Framework versions 2.0 SP2 through 4.5. The vulnerability stems from a missing array-size check during a memory copy operation, allowing remote code execution when exploited via crafted XBAP or .NET applications.

MitigationApply Microsoft security updates for .NET Framework once released. Consider disabling XAML browser applications (XBAP) in Internet Explorer and restricting untrusted .NET applications until the patch is 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:= 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
    Check the Windows Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v{version}\Install and SPLevel, or use the 'dotnet --version' command if .NET Core/5+ is present (though this CVE affects .NET Framework only)
    Affected if Version is 2.0 SP2 or higher through 4.5 (versions 2.0, 3.5, 3.5.1, 4.0, or 4.5)
  2. Determine if System.DirectoryServices.Protocols is in use
    Search application source code for 'using System.DirectoryServices.Protocols;' or 'S.DS.P' namespace imports, and check compiled assemblies using ildasm or a .NET decompiler for references to System.DirectoryServices.Protocols.dll
    Affected if The application or its dependencies reference and use the System.DirectoryServices.Protocols namespace
  3. Check if XBAP (XAML Browser Applications) are enabled
    In Internet Explorer, go to Internet Options > Security > Custom Level and check the 'Enable XAML browser applications' setting; also check HKCU\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_SECURITY_CSP for Group Policy overrides
    Affected if XBAP is enabled in Internet Explorer or allowed via policy, as this is one attack vector for the vulnerability
  4. Identify if untrusted .NET applications can execute
    Review .NET security policy settings (if .NET 3.5 or earlier): run 'caspol -list' to see code groups, and check if applications from the Internet or Intranet zones have full trust; for .NET 4.x, examine <runtime> security settings in machine.config
    Affected if Untrusted or partially trusted .NET code can run with full permissions, allowing exploitation via crafted applications

The environment is affected if .NET Framework versions 2.0 SP2 through 4.5 are installed AND applications using System.DirectoryServices.Protocols run, or XBAP/untrusted .NET applications are permitted.

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 .NET Framework once released. Consider disabling XAML browser applications (XBAP) in Internet Explorer and restricting untrusted .NET applications until the patch is deployed.

Recommended fix High confidence
  1. Open Windows Update or Microsoft Update on the affected system
  2. Search for security updates for Microsoft .NET Framework
  3. Install the applicable security update (MS13-004 or subsequent superseded updates) that addresses CVE-2013-0003
  4. Restart the system if prompted
  5. Verify the update was installed by checking the installed updates list

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

Fix this in .net Framework Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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