CVE-2013-0005
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 · uneditedThe WCF Replace function in the Open Data (aka OData) protocol implementation in Microsoft .NET Framework 3.5, 3.5 SP1, 3.5.1, and 4, and the Management OData IIS Extension on Windows Server 2012, allows remote attackers to cause a denial of service (resource consumption and daemon restart) via crafted values in HTTP requests, aka "Replace Denial of Service 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 confidenceThe WCF Replace function in the OData protocol implementation in Microsoft .NET Framework 3.5 through 4 and the Management OData IIS Extension on Windows Server 2012 contains a denial of service vulnerability. Remote attackers can send crafted values in HTTP requests to cause excessive resource consumption, resulting in service restart.
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= 3.5= 3.5.1= 4.0all versionsCVSS 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
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:N/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed .NET Framework versionCheck the Windows registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full for the Release value, or use 'reg query "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP" /s' to list installed versionsAffected if The installed version is 3.5, 3.5.1, or 4.0 (release values 30319 for .NET 4.0, or 378389/378675/378758 for .NET 4.5 which includes .NET 4.0 component)
-
Verify Management OData IIS Extension presenceCheck for the presence of Management OData IIS Extension by looking for the Microsoft.Management.Odata.dll assembly in the IIS global assembly cache or in the bin folder of Management OData IIS Extension application poolsAffected if The Management OData IIS Extension is installed on the system (all versions are affected)
-
Confirm OData endpoint exposure in IISReview IIS Manager or check applicationHost.config for OData protocol endpoints, specifically looking for WCF services that implement OData (typically endpoints with /odata/ or /servicename.svc/ URL patterns)Affected if OData-enabled WCF services are exposed via IIS and accessible over HTTP/HTTPS
A system is affected if it runs .NET Framework 3.5, 3.5.1, or 4.0 OR has the Management OData IIS Extension installed, AND has OData/WCF endpoints exposed through IIS that handle HTTP requests.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply Microsoft security updates for CVE-2013-0005 to affected .NET Framework versions and the Management OData IIS Extension. Consider rate limiting and request validation at the IIS level as a compensating control until patches are applied.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0005 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-0005 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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