Skip to content
Fencer Intel
high 7.5

CVE-2020-0969 in the critical feed json

ChakraCore RCE Vulnerability

published 6y ago modified 4mo ago also GHSA-jr84-p554-62pm , EUVD-2022-4424

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
13.3%
EPSS 13.3% chance of exploitation in 30 days, percentile 96%
public exploits
0
none known

Summary

A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge (HTML-based), aka 'Chakra Scripting Engine Memory Corruption Vulnerability'.

Patch / fix

  • nuget Microsoft.ChakraCore 1.11.18
  • microsoft chakracore 1.11.18

Is CVE-2020-0969 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 Fencer

Exploit prediction

13.30% 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.1 7.5 CVSS:3.1/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.1 7.5 CVSS:3.1/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.11.18
1.11.18

Affected products

  • Microsoft ChakraCore
  • Microsoft Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1803 for 32-bit Systems
  • Microsoft Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1803 for x64-based Systems
  • Microsoft Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1803 for ARM64-based Systems
  • Microsoft Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1809 for 32-bit Systems
  • Microsoft Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1809 for x64-based Systems
  • Microsoft Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1809 for ARM64-based Systems
  • Microsoft Microsoft Edge (EdgeHTML-based) on Windows Server 2019
  • Microsoft Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1909 for 32-bit Systems
  • Microsoft Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1909 for x64-based Systems
  • Microsoft Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1909 for ARM64-based Systems
  • Microsoft Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1709 for 32-bit Systems
  • Microsoft Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1709 for x64-based Systems
  • Microsoft Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1709 for ARM64-based Systems
  • Microsoft Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1903 for 32-bit Systems
  • Microsoft Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1903 for x64-based Systems
  • Microsoft Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1903 for ARM64-based Systems
  • Microsoft Microsoft Edge (EdgeHTML-based) on Windows 10 for 32-bit Systems
  • Microsoft Microsoft Edge (EdgeHTML-based) on Windows 10 for x64-based Systems
  • Microsoft Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1607 for 32-bit Systems
  • Microsoft Microsoft Edge (EdgeHTML-based) on Windows 10 Version 1607 for x64-based Systems
  • Microsoft Microsoft Edge (EdgeHTML-based) on Windows Server 2016

Classification

Weakness
  • CWE-787 Out-of-bounds Write
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

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.