CVE-2017-8608

Description

Microsoft browsers in Microsoft Windows Server 2008 and R2, Windows 8.1 and Windows RT 8.1, Windows Server 2012 and R2, Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016 allow an attacker to execute arbitrary code in the context of the current user when the JavaScript engines fail to render when handling objects in memory in Microsoft browsers, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-8598, CVE-2017-8596, CVE-2017-8610, CVE-2017-8601, CVE-2017-8618, CVE-2017-8619, CVE-2017-8603, CVE-2017-8604, CVE-2017-8605, CVE-2017-8595, CVE-2017-8606, CVE-2017-8607, and CVE-2017-8609

Link	Tags
http://www.securitytracker.com/id/1038848	third party advisory vdb entry
http://www.securitytracker.com/id/1038849	third party advisory vdb entry
https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/CVE-2017-8608	patch vendor advisory
http://www.securityfocus.com/bid/99412	third party advisory vdb entry

What is the severity of CVE-2017-8608?: CVE-2017-8608 has been scored as a high severity vulnerability.
How to fix CVE-2017-8608?: To fix CVE-2017-8608, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-8608 being actively exploited in the wild?: It is possible that CVE-2017-8608 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~22% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2017-8608?: CVE-2017-8608 affects Microsoft Corporation Microsoft Windows Server 2008 and R2, Windows 8.1 and Windows RT 8.1, Windows Server 2012 and R2, Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016..