HighGHSA-9824-rp6m-xx9wCVE-2019-0989

Chakra Scripting Engine Memory Corruption Vulnerability

Published 29 Mar 2021 · Updated 20 May 2025

Is your project on an affected Microsoft.ChakraCore?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<1.11.10
Fixed in
1.11.10
Update to the fixed version for your release line, for example:dotnet add package Microsoft.ChakraCore --version 1.11.10

Details

A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge (HTML-based). The vulnerability could corrupt memory in such a way that an attacker could execute arbitrary code in the context of the current user. An attacker who successfully exploited the vulnerability could gain the same user rights as the current user. If the current user is logged on with administrative user rights, an attacker who successfully exploited the vulnerability could take control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. In a web-based attack scenario, an attacker could host a specially crafted website that is designed to exploit the vulnerability through Microsoft Edge (HTML-based) and then convince a user to view the website. The attacker could also take advantage of compromised websites and websites that accept or host user-provided content or advertisements. These websites could contain specially crafted content that could exploit the vulnerability. The security update addresses the vulnerability by modifying how the Chakra scripting engine handles objects in memory.

Is GHSA-9824-rp6m-xx9w in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected Microsoft.ChakraCore, and gives you the command that fixes it.

More advisories for Microsoft.ChakraCore

  • HighCVE-2020-0813ChakraCore information disclosure vulnerability · 24 May 2022
  • HighCVE-2019-1002ChakraCore RCE via Out-of-bounds write · 24 May 2022
  • HighCVE-2019-1051Chakra Scripting Engine RCE via Out-of-bounds write · 24 May 2022
  • HighCVE-2019-1024Chakra Scripting Engine RCE Vulnerability · 24 May 2022
  • HighCVE-2019-1052Chakra Scripting Engine RCE via Out-of-bounds write · 24 May 2022
  • HighCVE-2021-42279Chakra Scripting Engine and ChakraCore Vulnerable to Memory Corruption · 24 May 2022
All 247 advisories for Microsoft.ChakraCore

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.