CVE-2017-11910: Buffer Overflow
ChakraCore and Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows Server 2016 allows an attacker to execute arbitrary code in the context of the current user, due to how the scripting engine handles objects in memory, aka "Scripting Engine Memory Corruption Vulnerability". An insufficient InlineCache check can lead to type confusion, which could potentially allow for remote code execution.
This CVE ID is unique from CVE-2017-11886, CVE-2017-11889, CVE-2017-11890, CVE-2017-11893, CVE-2017-11894, CVE-2017-11895, CVE-2017-11901, CVE-2017-11903, CVE-2017-11905, CVE-2017-11905, CVE-2017-11907, CVE-2017-11908, CVE-2017-11909, CVE-2017-11911, CVE-2017-11912, CVE-2017-11913, CVE-2017-11914, CVE-2017-11916, CVE-2017-11918, and CVE-2017-11930.
Other sources
ChakraCore and Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows Server 2016 allows an attacker to execute arbitrary code in the context of the current user, due to how the scripting engine handles objects in memory, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-11886, CVE-2017-11889, CVE-2017-11890, CVE-2017-11893, CVE-2017-11894, CVE-2017-11895, CVE-2017-11901, CVE-2017-11903, CVE-2017-11905, CVE-2017-11905, CVE-2017-11907, CVE-2017-11908, CVE-2017-11909, CVE-2017-11911, CVE-2017-11912, CVE-2017-11913, CVE-2017-11914, CVE-2017-11916, CVE-2017-11918, and CVE-2017-11930.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2017-11910?
CVE-2017-11910 is rated as critical due to the potential for arbitrary code execution by an attacker.
How do I fix CVE-2017-11910?
To fix CVE-2017-11910, update Microsoft ChakraCore to version 1.7.5 or later.
What platforms are affected by CVE-2017-11910?
CVE-2017-11910 affects Microsoft ChakraCore on various Windows 10 versions and Windows Server 2016.
Can CVE-2017-11910 be exploited remotely?
Yes, CVE-2017-11910 can be exploited remotely by a malicious web page or a malicious application.
Is there a workaround for CVE-2017-11910?
There are no known workarounds for CVE-2017-11910; the recommended action is to apply the security update.