CVE-2016-3367High

Microsoft security update for CVE-2016-3367 — Microsoft Silverlight 5

Published
September 13, 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-3367. This page also shows what EchelonGraph holds for CVE-2016-3367, 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)

✅ Updates Microsoft lists: 1 update

1 row: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
—Security Update—

🧭 EchelonGraph on CVE-2016-3367

EchelonGraph score
8.8 HIGH
CISA KEV
Not listed
Fix status
A fix is available — apply it.

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

StringBuilder in Microsoft Silverlight 5 before 5.1.50709.0 does not properly allocate memory for string-insert and string-append operations, which allows remote attackers to execute arbitrary code via a crafted web site, aka "Microsoft Silverlight Memory Corruption Vulnerability."

Published by Microsoft Corporation, the CVE Numbering Authority that assigned CVE-2016-3367, 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 (2)