CVE-2016-7208CriticalMicrosoft CVSS 4.2CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N/E:P/RL:O/RC:C

Microsoft security update for CVE-2016-7208 — Microsoft Edge (EdgeHTML-based) on Windows

Published
November 8, 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-7208. This page also shows what EchelonGraph holds for CVE-2016-7208, 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 products5

  • Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1511 for 32-bit Systems
  • Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1511 for x64-based Systems
  • Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1607 for 32-bit Systems
  • Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1607 for x64-based Systems
  • Microsoft Edge (EdgeHTML-based) on Windows Server 2016

✅ Updates Microsoft lists: 2 KB articles

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

KB articleUpdateFixed build
KB3198586Security Update—
KB3200970Security Update—

🧭 EchelonGraph on CVE-2016-7208

EchelonGraph score
7.5 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

The Chakra JavaScript scripting engine in Microsoft Edge allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "Scripting Engine Memory Corruption Vulnerability," a different vulnerability than CVE-2016-7200, CVE-2016-7201, CVE-2016-7202, CVE-2016-7203, CVE-2016-7240, CVE-2016-7242, and CVE-2016-7243.

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