CVE-2017-11894Not scoredCWE-119

CVE-2017-11894: Microsoft Corporation ChakraCore, Microsoft Edge, Internet Explorer vulnerability

Microsoft Corporation · ChakraCore, Microsoft Edge, Internet Explorer

Affected: Microsoft Corporation ChakraCore, Microsoft Edge, Internet Explorer · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

8.5%probability of exploitation in the next 30 days

95th percentile

050100

Higher than 95% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

ChakraCore, and Internet Explorer in Microsoft Windows 7 SP1, Windows Server 2008 and R2 SP1, Windows 8.1 and Windows RT 8.1, Windows Server 2012 and R2, and and Internet Explorer adn Microsoft Edge in Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows Server 2016 allows an attacker to gain the same user rights as 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-11895, CVE-2017-11901, CVE-2017-11903, CVE-2017-11905, CVE-2017-11907, CVE-2017-11908, CVE-2017-11909, CVE-2017-11910, CVE-2017-11911, CVE-2017-11912, CVE-2017-11913, CVE-2017-11914, CVE-2017-11916, CVE-2017-11918, and CVE-2017-11930.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

Microsoft Corporation · ChakraCore, Microsoft Edge, Internet ExplorerMicrosoft Windows 7 SP1, Windows Server 2008 and R2 SP1, Wi…

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Memory Buffer Bounds · Memory Corruption
Vendor: Microsoft Corporation
Published: December 2017
Band: Possible (1 to 10%), December 2017

CoverageNo articles yet

No CyberSIXT article names CVE-2017-11894 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.