CVE-2018-8391 in the critical feed json
ChakraCore RCE Vulnerability
published 8y ago modified 4mo ago also GHSA-788w-269g-j92q , EUVD-2022-2950
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 11.3%
- EPSS 11.3% chance of exploitation in 30 days, percentile 95%
- public exploits
- 0
- none known
Summary
A remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka "Scripting Engine Memory Corruption Vulnerability." This affects ChakraCore. This CVE ID is unique from CVE-2018-8354, CVE-2018-8456, CVE-2018-8457, CVE-2018-8459.
Patch / fix
- nuget Microsoft.ChakraCore 1.11.1
Is CVE-2018-8391 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 FencerExploit prediction
11.27% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-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.11.1 |
1.11.1 |
Affected products
- Microsoft ChakraCore
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2018-8391
web, patch, vendor-advisory
-
securityfocus.com
/bid/105231
vdb-entry, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2018-8391
advisory
-
github.com
/chakra-core/ChakraCore
package
-
web.archive.org
/web/20210419154033/http://www.securityfocus.com/bid/105231
web
Sources
- CVE List CVE-2018-8391
- GitHub Advisory GHSA-788w-269g-j92q
- NVD CVE-2018-8391
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.