CVE-2013-0074
Microsoft Silverlight Double Dereference Vulnerability
Microsoft Silverlight
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."
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 25 May 2022. US federal agencies were required to remediate it by 15 June 2022. CISA records this vulnerability as known to be used in ransomware campaigns.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 78.9%, which is higher than 99.6% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2013-0074 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2013-0074.
What does CVE-2013-0074 affect?
CVE-2013-0074 affects Microsoft Silverlight. 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."
How severe is CVE-2013-0074?
CVE-2013-0074 is rated HIGH with a CVSS base score of 7.8. EPSS puts the probability of exploitation in the next 30 days at 78.9%, higher than 99.6% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 15 June 2022.
How should organisations respond to CVE-2013-0074?
Apply the vendor patch for Microsoft Silverlight as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.