CVE-2018-8283 in the critical feed json
ChakraCore RCE Vulnerability
published 2018-07-11 8 y ago modified 2026-06-17 4 mo ago also GHSA-ch84-pxpj-7hhm , EUVD-2022-3582
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 15.2%
- EPSS 15.2% chance of exploitation in 30 days, percentile 96%
- 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-8242, CVE-2018-8287, CVE-2018-8288, CVE-2018-8291, CVE-2018-8296, CVE-2018-8298.
Patch / fix
- nuget Microsoft.ChakraCore 1.10.1
- microsoft chakracore 1.10.1
Exploit prediction
15.22% chance of exploitation in the next 30 days, higher than 96% 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.10.1 |
1.10.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-8283
web, patch, vendor-advisory
-
github.com
/chakra-core/ChakraCore/pull/5444
web
-
github.com
/chakra-core/ChakraCore/commit/b2f092ea42744d569fd102e8dd85d5524269bdd0
web
-
securityfocus.com
/bid/104633
vdb-entry, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2018-8283
advisory
-
web.archive.org
/web/20210125211350/http://www.securityfocus.com/bid/104633
web
Sources
- CVE List CVE-2018-8283
- GitHub Advisory GHSA-ch84-pxpj-7hhm
- NVD CVE-2018-8283
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.