Skip to content
Fencer Intel
high 7.5

CVE-2017-11911 in the critical feed json

ChakraCore RCE Vulnerability

published 8y ago modified 4mo ago also GHSA-qfcq-4vv7-9mq7 , EUVD-2022-4958

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
65.5%
EPSS 65.5% chance of exploitation in 30 days, percentile 99.2%
public exploits
1
Exploit-DB

Summary

ChakraCore and Windows 10 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-11910, CVE-2017-11912, CVE-2017-11913, CVE-2017-11914, CVE-2017-11916, CVE-2017-11918, and CVE-2017-11930.

Patch / fix

  • nuget Microsoft.ChakraCore 1.7.5
  • microsoft chakracore 1.7.5

Is CVE-2017-11911 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. Published
  2. First public exploit (EDB-43468)

Exploit prediction

65.46% chance of exploitation in the next 30 days, higher than 99.2% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-43468 Microsoft Edge Chakra - 'asm.js' Out-of-Bounds Read dos, 2018-01-09

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 7.6 AV:N/AC:H/Au:N/C:C/I:C/A:C
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
nuget Microsoft.ChakraCore
<1.7.5
1.7.5

Affected products

  • Microsoft Corporation ChakraCore, Microsoft Edge

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.