CVE-2017-0223 in the critical feed json
ChakraCore RCE Vulnerability
published 2017-05-15 9 y ago modified 2026-06-17 4 mo ago also GHSA-448h-7hmp-99fg , EUVD-2022-2292
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 14.7%
- EPSS 14.7% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known
Summary
A remote code execution vulnerability exists in Microsoft Chakra Core in the way JavaScript engines render when handling objects in memory. aka "Scripting Engine Memory Corruption Vulnerability". This vulnerability is unique from CVE-2017-0252.
Patch / fix
- nuget Microsoft.ChakraCore 1.4.4
- github.com/chakra-core/ChakraCore@f74773f commit
- github.com/Microsoft/ChakraCore#2959 pull request
- github.com/chakra-core/ChakraCore#2959 pull request
Exploit prediction
14.68% 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 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| 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.4.4 |
1.4.4 |
Affected products
- Microsoft Corporation Chakra Core
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
github.com
/Microsoft/ChakraCore/pull/2959
web, patch, third-party-advisory
-
github.com
/chakra-core/ChakraCore/pull/2959
web
-
github.com
/chakra-core/ChakraCore/commit/f74773f4520adff6b70a7d445417aa9769f61fa6
web
-
securitytracker.com
/id/1038425
vdb-entry
-
nvd.nist.gov
/vuln/detail/CVE-2017-0223
advisory
-
github.com
/chakra-core/ChakraCore
package
-
web.archive.org
/web/20210124184849/http://www.securitytracker.com/id/1038425
web
Sources
- CVE List CVE-2017-0223
- GitHub Advisory GHSA-448h-7hmp-99fg
- NVD CVE-2017-0223
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.