CVE-2013-1336 json
The 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 all…
published 13y ago modified 4mo ago also EUVD-2013-1376
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 19.3%
- EPSS 19.3% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known
Summary
The 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."
Is CVE-2013-1336 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
19.26% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2013/ms13-040
vendor-advisory
-
us-cert.gov
/ncas/alerts/TA13-134A
third-party-advisory, us-government-resource
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A16559
vdb-entry, signature
Sources
- CVE List CVE-2013-1336
- NVD CVE-2013-1336
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.