CVE-2016-3199 in the critical feed json
ChakraCore RCE Vulnerability
published 2016-06-16 10 y ago modified 2026-06-17 4 mo ago also GHSA-vfjw-crcq-q92v , EUVD-2022-5349
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 26.6%
- EPSS 26.6% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
The Chakra JavaScript engine in Microsoft Edge allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "Scripting Engine Memory Corruption Vulnerability," a different vulnerability than CVE-2016-3214.
Patch / fix
Exploit prediction
26.59% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
| GitHub | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| nuget | Microsoft.ChakraCore | <1.2.0.0 |
1.2.0.0 |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
github.com
/chakra-core/ChakraCore/commit/bcd950efee487bdfd73cd1282de4e02e82e62629
web
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2016/ms16-068
vendor-advisory, web
-
zerodayinitiative.com
/advisories/ZDI-16-367
web
-
zerodayinitiative.com
/advisories/ZDI-16-368
web
-
securitytracker.com
/id/1036099
vdb-entry
-
nvd.nist.gov
/vuln/detail/CVE-2016-3199
advisory
-
github.com
/chakra-core/ChakraCore
package
-
web.archive.org
/web/20211129115034/http://www.securitytracker.com/id/1036099
web
Sources
- CVE List CVE-2016-3199
- GitHub Advisory GHSA-vfjw-crcq-q92v
- NVD CVE-2016-3199
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.