CVE-2018-0931 in the critical feed json
ChakraCore RCE Vulnerability
published 2018-03-14 8 y ago modified 2026-06-17 4 mo ago also GHSA-h575-j3ph-hjvc , EUVD-2022-4066
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 11.4%
- EPSS 11.4% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known
Summary
ChakraCore and Microsoft Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows Server 2016 allows remote code execution, due to how the Chakra scripting engine handles objects in memory, aka "Chakra Scripting Engine Memory Corruption Vulnerability". This CVE ID is unique from CVE-2018-0872, CVE-2018-0873, CVE-2018-0874, CVE-2018-0930, CVE-2018-0933, CVE-2018-0934, CVE-2018-0936, and CVE-2018-0937.
Patch / fix
- nuget Microsoft.ChakraCore 1.8.2
Exploit prediction
11.44% chance of exploitation in the next 30 days, higher than 96% 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 | 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.8.2 |
1.8.2 |
Affected products
- Microsoft Corporation ChakraCore, Microsoft Edge
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2018-0931
web, patch, vendor-advisory
-
github.com
/chakra-core/ChakraCore/commit/46c98f0645dfa58654036c8a7417e67e81e4706a
web
-
securityfocus.com
/bid/103273
vdb-entry, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2018-0931
advisory
-
github.com
/chakra-core/ChakraCore
package
-
web.archive.org
/web/20210124144712/http://www.securityfocus.com/bid/103273
web
Sources
- CVE List CVE-2018-0931
- GitHub Advisory GHSA-h575-j3ph-hjvc
- NVD CVE-2018-0931
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.