CVE-2018-8139 in the critical feed json
ChakraCore RCE Vulnerability
published 8y ago modified 4mo ago also GHSA-5hxp-3237-j2hp , EUVD-2022-2604
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 66.3%
- EPSS 66.3% chance of exploitation in 30 days, percentile 99.2%
- public exploits
- 1
- Exploit-DB
Summary
A remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Microsoft Edge, aka "Scripting Engine Memory Corruption Vulnerability." This affects Microsoft Edge, ChakraCore. This CVE ID is unique from CVE-2018-0945, CVE-2018-0946, CVE-2018-0951, CVE-2018-0953, CVE-2018-0954, CVE-2018-0955, CVE-2018-1022, CVE-2018-8114, CVE-2018-8122, CVE-2018-8128, CVE-2018-8137.
Patch / fix
- nuget Microsoft.ChakraCore 1.8.4
Is CVE-2018-8139 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 FencerTimeline
- Published
- First public exploit (EDB-45012)
Exploit prediction
66.31% chance of exploitation in the next 30 days, higher than 99.2% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-45012 Microsoft Edge Chakra JIT - BoundFunction::NewInstance Out-of-Bounds Read dos, 2018-07-12
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.4 |
1.8.4 |
Affected products
- Microsoft Microsoft Edge
- Microsoft ChakraCore
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2018-8139
web, patch, vendor-advisory
-
github.com
/chakra-core/ChakraCore/commit/ee5dfabc51728f97f6d69e89c88af088251b6b76
web
-
exploit-db.com
/exploits/45012/
exploit, third-party-advisory, vdb-entry
-
securityfocus.com
/bid/103977
vdb-entry, third-party-advisory
-
securitytracker.com
/id/1040844
vdb-entry, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2018-8139
advisory
-
github.com
/chakra-core/ChakraCore
package
-
web.archive.org
/web/20210124164247/http://www.securityfocus.com/bid/103977
web
-
web.archive.org
/web/20211204185256/http://www.securitytracker.com/id/1040844
web
-
exploit-db.com
/exploits/45012
web
Sources
- CVE List CVE-2018-8139
- GitHub Advisory GHSA-5hxp-3237-j2hp
- NVD CVE-2018-8139
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.