CVE-2017-11821 json
ChakraCore RCE Vulnerability
published 9y ago modified 4mo ago also GHSA-rhwh-jw9h-4m49 , EUVD-2022-5179
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 8.8%
- EPSS 8.8% chance of exploitation in 30 days, percentile 95%
- public exploits
- 0
- none known
Summary
ChakraCore and Microsoft Edge in Microsoft Windows 10 1703 allows an attacker to execute arbitrary code in the context of the current user, due to how the scripting engine handles objects in memory, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-11792, CVE-2017-11793, CVE-2017-11796, CVE-2017-11797, CVE-2017-11798, CVE-2017-11799, CVE-2017-11800, CVE-2017-11801, CVE-2017-11802, CVE-2017-11804, CVE-2017-11805, CVE-2017-11806, CVE-2017-11807, CVE-2017-11808, CVE-2017-11809, CVE-2017-11810, CVE-2017-11811, and CVE-2017-11812.
Patch / fix
- nuget Microsoft.ChakraCore 1.7.3
Is CVE-2017-11821 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
8.76% 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.7.3 |
1.7.3 |
Affected products
- Microsoft Corporation ChakraCore, 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-11821
web, patch, vendor-advisory
-
github.com
/chakra-core/ChakraCore/pull/3917
web
-
github.com
/chakra-core/ChakraCore/commit/2a07ca62db5618f4c75fd7749a6b49c831957d84
web
-
securitytracker.com
/id/1039529
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/101123
vdb-entry, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2017-11821
advisory
-
github.com
/chakra-core/ChakraCore
package
-
web.archive.org
/web/20210124105815/http://www.securityfocus.com/bid/101123
web
-
web.archive.org
/web/20211208040741/http://www.securitytracker.com/id/1039529
web
Sources
- CVE List CVE-2017-11821
- GitHub Advisory GHSA-rhwh-jw9h-4m49
- NVD CVE-2017-11821
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.