CVE-2013-0074: Microsoft Silverlight Double Dereference
Microsoft Silverlight · listed in the CISA catalog of actively exploited vulnerabilities since 2022-05-25.
- CVSS v3.1 (CISA ADP)
- 7.8
- high
- EPSS (exploit probability, 30 days)
- 79%
- higher than 99.6% of all CVEs
- Added to CISA KEV
- 2022-05-25
- US federal due date 2022-06-15
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2013-0074 explained
CVE-2013-0074 is a pointer validation flaw in Microsoft Silverlight 5 and 5 Developer Runtime during HTML object rendering. A crafted Silverlight application can lead to arbitrary code execution. CISA lists it as known exploited, with known ransomware use, and states the product is end-of-life.
Impact
An attacker who gets a user to open a crafted Silverlight application can execute arbitrary code. User interaction is required, and no privileges are needed. Successful exploitation gives high impact to confidentiality, integrity and availability. CISA rates the technical impact as total and the attack as not automatable. Attackers are known to exploit this vulnerability, including in ransomware campaigns.
Who is affected
The description names Microsoft Silverlight 5 and 5 Developer Runtime before 5.1.20125.0 as affected. The CVE record itself lists no affected versions and names no fixed version for Microsoft Silverlight. CISA states that the impacted product is end-of-life.
Written with AI from the data on this page and checked against it automatically.
Official description
Microsoft Silverlight 5, and 5 Developer Runtime, before 5.1.20125.0 does not properly validate pointers during HTML object rendering, which allows remote attackers to execute arbitrary code via a crafted Silverlight application, aka "Silverlight Double Dereference Vulnerability."
CISA required action: The impacted product is end-of-life and should be disconnected if still in use.
CISA notes
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: docs.microsoft.com/en-us/security-updates/securitybulleti…
- CISA's deadline for US federal agencies: 2022-06-15 (passed) – a useful benchmark for everyone else, too.
What to do
- Identify all systems that still have Microsoft Silverlight installed.
- Disconnect or uninstall Microsoft Silverlight, as CISA requires, because the product is end-of-life.
- Replace applications that depend on Silverlight with supported alternatives.
- Check systems that ran Silverlight for signs of compromise, given known ransomware use.
- Review the vendor advisory for historical details on the issue.
CISA states that Microsoft Silverlight is end-of-life and should be disconnected if still in use. Do not wait for a fix. Remove Silverlight from all systems, move dependent applications to supported technology, and check affected hosts for signs of compromise.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Questions about CVE-2013-0074
- Is CVE-2013-0074 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-05-25 and reports known use in ransomware campaigns.
- Can I patch Silverlight instead of removing it?
- CISA states the product is end-of-life and should be disconnected if still in use. Removal is the required action, not patching.
- Does exploitation require user action?
- Yes. A user must run a crafted Silverlight application. No privileges are required, and successful exploitation allows arbitrary code execution.
Written with AI from the data on this page and checked against it automatically.
References
Vendor
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.