Microsoft security update for CVE-2017-0093 — Microsoft Edge (EdgeHTML-based) on Windows 10
🔗 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-2017-0093. This page also shows what EchelonGraph holds for CVE-2017-0093, 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 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 10 Version 1703 for 32-bit Systems
- Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1703 for x64-based Systems
✅ Updates Microsoft lists: 3 KB articles
3 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.
🧭 EchelonGraph on CVE-2017-0093
- 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
A remote code execution vulnerability in Microsoft Edge exists in the way that the Scripting Engine renders when handling objects in memory in Microsoft browsers. The vulnerability could corrupt memory in such a way that an attacker could execute arbitrary code in the context of the current user, aka "Scripting Engine Memory Corruption Vulnerability." This CVE ID is unique from CVE-2017-0201.
Published by Microsoft Corporation, the CVE Numbering Authority that assigned CVE-2017-0093, 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).