High severity vulnerability that affects Microsoft.ChakraCore
Published 9 Apr 2019 · Updated 8 Nov 2023
Is your project on an affected Microsoft.ChakraCore?
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.7
- Fixed in
- 1.11.7
dotnet add package Microsoft.ChakraCore --version 1.11.7Details
A remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Microsoft Edge, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0609, CVE-2019-0639, CVE-2019-0680, CVE-2019-0769, CVE-2019-0770, CVE-2019-0771, CVE-2019-0783.
Is GHSA-3w9q-c44j-37jj 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
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.