Skip to content
Fencer Intel
high 7.5

CVE-2017-11870 in the critical feed json

Chakra Core vulnerable to privilege escalation when writing to JavaScript null scope objects

published 8y ago modified 4mo ago also GHSA-9f2p-wm46-6m5f , EUVD-2022-3357

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

Summary

ChakraCore and Microsoft Edge in Windows 10 1703, 1709, and Windows Server, version 1709 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-11836, CVE-2017-11837, CVE-2017-11838, CVE-2017-11839, CVE-2017-11840, CVE-2017-11841, CVE-2017-11843, CVE-2017-11846, CVE-2017-11858, CVE-2017-11859, CVE-2017-11861, CVE-2017-11862, CVE-2017-11866, CVE-2017-11869, CVE-2017-11871, and CVE-2017-11873.

Patch / fix

  • nuget Microsoft.ChakraCore 1.7.4

Is CVE-2017-11870 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-43182)

Exploit prediction

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

Exploits and checks

  • EDB-43182 Microsoft Edge Chakra JIT - Incorrect Function Declaration Scope dos, 2017-11-27

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.4
1.7.4

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.