CVE-2017-0235 in the critical feed json
ChakraCore RCE Vulnerability
published 2017-05-12 9 y ago modified 2026-06-17 4 mo ago also GHSA-rm8g-7g54-w6fh , EUVD-2022-5200
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 11.1%
- EPSS 11.1% chance of exploitation in 30 days, percentile 95%
- public exploits
- 0
- none known
Summary
A remote code execution vulnerability exists in Microsoft Edge in the way that the Chakra JavaScript engine renders when handling objects in memory, aka "Scripting Engine Memory Corruption Vulnerability." This CVE ID is unique from CVE-2017-0224, CVE-2017-0228, CVE-2017-0229, CVE-2017-0230, CVE-2017-0234, CVE-2017-0236, and CVE-2017-0238.
Patch / fix
- nuget Microsoft.ChakraCore 1.4.4
Exploit prediction
11.06% chance of exploitation in the next 30 days, higher than 95% 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.4.4 |
1.4.4 |
Affected products
- Microsoft Corporation Microsoft Edge
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2017-0235
web, patch, vendor-advisory
-
github.com
/chakra-core/ChakraCore/pull/2959
web
-
github.com
/chakra-core/ChakraCore/commit/f022afb8246acc98e74a887bb655ac512caf6e72
web
-
securityfocus.com
/bid/98230
vdb-entry, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2017-0235
advisory
-
github.com
/chakra-core/ChakraCore
package
-
web.archive.org
/web/20210124044045/http://www.securityfocus.com/bid/98230
web
Sources
- CVE List CVE-2017-0235
- GitHub Advisory GHSA-rm8g-7g54-w6fh
- NVD CVE-2017-0235
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.