HighGHSA-92j2-gg59-4572CVE-2016-3382

ChakraCore RCE Vulnerability

Published 14 May 2022 · Updated 16 Feb 2024

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.2.1
Fixed in
1.2.1
Update to the fixed version for your release line, for example:dotnet add package Microsoft.ChakraCore --version 1.2.1

Details

The scripting engines in Microsoft Internet Explorer 9 through 11 and Microsoft Edge allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, as demonstrated by the Chakra JavaScript engine, aka "Scripting Engine Memory Corruption Vulnerability."

Is GHSA-92j2-gg59-4572 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.