Skip to content
Fencer Intel
high 7.5

CVE-2020-0833 json

Out-of-bounds write in ChakraCore

published 6y ago modified 4mo ago also GHSA-86gw-g9jv-8vfg , EUVD-2021-1449

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

Summary

A remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Internet Explorer, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0768, CVE-2020-0823, CVE-2020-0825, CVE-2020-0826, CVE-2020-0827, CVE-2020-0828, CVE-2020-0829, CVE-2020-0830, CVE-2020-0831, CVE-2020-0832, CVE-2020-0848.

Patch / fix

  • nuget Microsoft.ChakraCore 1.11.17

Is CVE-2020-0833 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

8.68% 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.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.17
1.11.17

Affected products

  • Microsoft Internet Explorer 11
  • Microsoft Internet Explorer 11 on Windows 10 Version 1909 for 32-bit Systems
  • Microsoft Internet Explorer 11 on Windows 10 Version 1909 for x64-based Systems
  • Microsoft Internet Explorer 11 on Windows 10 Version 1909 for ARM64-based Systems
  • Microsoft Internet Explorer 11 on Windows 10 Version 1903 for 32-bit Systems
  • Microsoft Internet Explorer 11 on Windows 10 Version 1903 for x64-based Systems
  • Microsoft Internet Explorer 11 on Windows 10 Version 1903 for ARM64-based Systems
  • Microsoft Internet Explorer 11 on Windows Server 2012

Classification

Weakness

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.