CVE-2016-0034Critical

Microsoft advisory for CVE-2016-0034 — Microsoft Silverlight 5

Published
January 12, 2016
Last Modified
—

🔗 CVE IDs covered (1)

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2016-0034. This page also shows what EchelonGraph holds for CVE-2016-0034, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products6

  • Microsoft Silverlight 5 Developer Runtime when installed on Apple Mac OS (Intel-based)
  • Microsoft Silverlight 5 Developer Runtime when installed on Microsoft Windows (32-bit)
  • Microsoft Silverlight 5 Developer Runtime when installed on Microsoft Windows (x64-based)
  • Microsoft Silverlight 5 when installed on Apple Mac OS (Intel-based)
  • Microsoft Silverlight 5 when installed on Microsoft Windows (32-bit)
  • Microsoft Silverlight 5 when installed on Microsoft Windows (x64-based)

🧭 EchelonGraph on CVE-2016-0034

EchelonGraph score
9.0 CRITICAL
CISA KEV
Listed since May 25, 2022
Fix status
A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Description from the CVE record (CVE.org), as published by its numbering authority

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

Published by Microsoft Corporation, the CVE Numbering Authority that assigned CVE-2016-0034, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (1)