CVE-2013-1336
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 Common Language Runtime (CLR) in Microsoft .NET Framework 2.0 SP2, 3.5, 3.5.1, 4, and 4.5 does not properly check signatures, which allows remote attackers to make undetected changes to signed XML documents via unspecified vectors that preserve signature validity, aka "XML Digital Signature Spoofing 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 · moderate confidenceThe CLR in Microsoft .NET Framework 2.0 SP2 through 4.5 fails to properly validate XML digital signatures, allowing attackers to modify the content of signed XML documents while keeping the cryptographic signature valid. This enables XML Digital Signature spoofing where the integrity of signed documents cannot be trusted.
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= 2.0= 3.5= 3.5.1= 4.0= 4.5CVSS 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
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
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.
-
Check if .NET Framework is installedOpen Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v\ or check for the presence of .NET Framework directories in C:\Windows\Microsoft.NET\FrameworkAffected if No .NET Framework installation is found, the system is not affected by this specific vulnerability
-
Identify installed .NET Framework versionsRun reg query "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v\Version" /s in Command Prompt or use PowerShell Get-ChildItem -Path 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP' -Recurse | Get-ItemProperty -Name VersionAffected if The output shows version 2.0, 3.5, 3.5.1, 4.0, or 4.5 installed (including their service packs)
-
Confirm version falls within affected rangeCross-reference detected version numbers with the affected versions: 2.0 SP2 and later 2.x, 3.5, 3.5.1, 4.0, 4.5Affected if Installed version is 2.0 SP2 or later 2.x, or any version of 3.5, 3.5.1, 4.0, or 4.5
A system is affected if it has any version of .NET Framework 2.0 SP2 or later, 3.5, 3.5.1, 4.0, or 4.5 installed, as these versions contain the vulnerable XML signature validation code.
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 affected .NET Framework versions. For critical XML workflows, implement application-level content validation independent of XML signature verification and add secondary integrity checks.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1336 — 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-1336 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