CVE-2018-0818 json
ChakraCore RCE Vulnerability
published 2018-01-10 8 y ago modified 2026-06-17 4 mo ago also GHSA-fv8m-p45w-gf38 , EUVD-2022-3837
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.7%
- EPSS 3.7% chance of exploitation in 30 days, percentile 89%
- public exploits
- 0
- none known
Summary
Microsoft ChakraCore allows an attacker to bypass Control Flow Guard (CFG) in conjunction with another vulnerability to run arbitrary code on a target system, due to how the Chakra scripting engine handles accessing memory, aka "Scripting Engine Security Feature Bypass".
Patch / fix
- nuget Microsoft.ChakraCore 1.8.0
- github.com/chakra-core/ChakraCore#4427 commit
- github.com/chakra-core/ChakraCore#4427 pull request
Exploit prediction
3.69% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-08).
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 | 8.5 | AV:N/AC:M/Au:S/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.8.0 |
1.8.0 |
Affected products
- Microsoft Corporation ChakraCore
References
-
github.com
/chakra-core/ChakraCore/pull/4427
web
-
github.com
/chakra-core/ChakraCore/pull/4427/commits/84368681cf5cf1d33364638e2cd463ad1b13eba6
web
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2018-0818
web, vendor-advisory
-
securityfocus.com
/bid/102412
vdb-entry, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2018-0818
advisory
-
github.com
/chakra-core/ChakraCore
package
-
web.archive.org
/web/20210124130147/http://www.securityfocus.com/bid/102412
web
Sources
- CVE List CVE-2018-0818
- GitHub Advisory GHSA-fv8m-p45w-gf38
- NVD CVE-2018-0818
Fencer Vulns 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.