CVE-2018-8500 in the critical feed json
ChakraCore RCE Vulnerability
published 8y ago modified 4mo ago also GHSA-fw42-4mq4-4qpq , EUVD-2022-3843
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 18.5%
- EPSS 18.5% chance of exploitation in 30 days, percentile 97%
- 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.
Patch / fix
- nuget Microsoft.ChakraCore 1.11.2
Is CVE-2018-8500 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
18.47% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
| GitHub | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| nuget | Microsoft.ChakraCore | <1.11.2 |
1.11.2 |
Affected products
- Microsoft ChakraCore
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2018-8500
web, patch, vendor-advisory
-
github.com
/chakra-core/ChakraCore/pull/5764
web
-
github.com
/chakra-core/ChakraCore/commit/cd84a0b85b4b2bcf1653c7bfd5426bbc72b2b216
web
-
securityfocus.com
/bid/105463
vdb-entry, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2018-8500
advisory
-
github.com
/chakra-core/ChakraCore
package
-
web.archive.org
/web/20210124210846/http://www.securityfocus.com/bid/105463
web
Sources
- CVE List CVE-2018-8500
- GitHub Advisory GHSA-fw42-4mq4-4qpq
- NVD CVE-2018-8500
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.