CVE-2018-0925 in the critical feed json
ChakraCore RCE Vulnerability
published 8y ago modified 4mo ago also GHSA-5q2v-52gc-4w7p , EUVD-2022-2636
- 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 allows remote code execution, due to how the ChakraCore scripting engine handles objects in memory, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID is unique from CVE-2018-0876, CVE-2018-0889, CVE-2018-0893, and CVE-2018-0935.
Patch / fix
- nuget Microsoft.ChakraCore 1.8.2
Is CVE-2018-0925 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.44% 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.8.2 |
1.8.2 |
Affected products
- Microsoft Corporation ChakraCore
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2018-0925
web, patch, vendor-advisory
-
securityfocus.com
/bid/103287
vdb-entry, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2018-0925
advisory
-
github.com
/chakra-core/ChakraCore
package
-
web.archive.org
/web/20210124144841/http://www.securityfocus.com/bid/103287
web
Sources
- CVE List CVE-2018-0925
- GitHub Advisory GHSA-5q2v-52gc-4w7p
- NVD CVE-2018-0925
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.