LiveActive security incident?Get immediate response
CVE Record

CVE-2013-1336: The Common Language Runtime (CLR) in Microsoft .NET Framework 2.0 SP2, 3.5, 3.5.1, 4, and 4.5 does not prop...

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."

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This flaw affected Microsoft .NET Framework’s handling of XML digital signatures. An attacker could alter a signed XML document in a way that still appeared valid, undermining trust in signed data. The biggest concern is business processes that rely on signed XML for integrity or authorization decisions. Exposure is most likely on legacy Windows systems running the listed .NET Framework versions, especially applications that validate or trust signed XML documents. The provided affected-product metadata is incomplete, so inventory should be tied to Microsoft MS13-040 and local package evidence. Address during legacy-platform and application-risk remediation. Urgency rises if signed XML supports financial, identity, legal, or authorization workflows. No active exploitation is shown in the provided sources, but integrity bypass of trusted documents can create material business risk. Mitigation focus: Apply Microsoft’s MS13-040 security update for affected .NET Framework versions.; Inventory systems running .NET Framework 2.0 SP2, 3.5, 3.5.1, 4, or 4.5.; Prioritize applications that consume signed XML for trust, authorization, or transaction integrity..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2013-1336 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.