Microsoft browsers in Microsoft Windows 7 SP1, Windows Server 2008 R2 SP1, Windows 8.1 and Windows RT 8.1, Windows…
No fixed version listed yet.Check the vendor advisory. References ↓
Microsoft Corporation · Microsoft Scripting Engine
The Microsoft Scripting Engine, the JavaScript engine used by Microsoft browsers on several Windows client and server releases, contains a memory corruption flaw in how it handles objects in memory during rendering. An attacker can execute arbitrary code in the context of the current user, and the conditions required for exploitation are not specified in the available data.
Official description · CVE.org
Microsoft browsers in Microsoft Windows 7 SP1, Windows Server 2008 R2 SP1, Windows 8.1 and Windows RT 8.1, Windows Server 2012 and R2, Windows 10 Gold, 1511, 1607, 1703, and Windows Server 2016 allow an attacker to execute arbitrary code in the context of the current user due to the way that JavaScript engines render when handling objects in memory, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-8634, CVE-2017-8636, CVE-2017-8638, CVE-2017-8639, CVE-2017-8640, CVE-2017-8641, CVE-2017-8645, CVE-2017-8646, CVE-2017-8647, CVE-2017-8655, CVE-2017-8656, CVE-2017-8657, CVE-2017-8670, CVE-2017-8671, CVE-2017-8672, and CVE-2017-8674.
- Exploited
- Not confirmed
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Public exploit code (Exploit-DB) appeared 9 days after disclosure. No confirmed exploitation is recorded.
- Disclosedday 0
- Public exploit codeExploit-DB+9 days
Affected versions and fixes
as published in the CVE recordMicrosoft Corporation Microsoft Scripting Engine
Affected: Microsoft Windows 7 SP1, Windows Server 2008 R2 SP1, Windows 8.1 and Windows RT 8.1, Windows Server 2012 and R2, Windows 10 Gold, 1511, 1607, 1703, and Windows Server 2016.