HIGH · CVSS 8.8 CISA Known Exploited Vulnerability

CVE-2016-0034

Microsoft Silverlight Runtime Remote Code Execution Vulnerability

Microsoft Silverlight

Microsoft Silverlight 5 before 5.1.41212.0 mishandles negative offsets during decoding, which allows remote attackers to execute arbitrary code or cause a denial of service (object-header corruption) via a crafted web site, aka "Silverlight Runtime Remote Code Execution Vulnerability."

CVSS
8.8
HIGH
EPSS
69.4%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
13 Jan 2016
NVD

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 69.4%, which is higher than 99.3% 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:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Frequently asked questions

Is CVE-2016-0034 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2016-0034.

What does CVE-2016-0034 affect?

CVE-2016-0034 affects Microsoft Silverlight. Microsoft Silverlight 5 before 5.1.41212.0 mishandles negative offsets during decoding, which allows remote attackers to execute arbitrary code or cause a denial of service (object-header corruption) via a crafted web site, aka "Silverlight Runtime Remote Code Execution Vulnerability."

How severe is CVE-2016-0034?

CVE-2016-0034 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 69.4%, higher than 99.3% 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-2016-0034?

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.