Skip to content

GHSA-wgw2-wwq8-c7wf GHSA-wgw2-wwq8-c7wf

ChakraCore RCE Vulnerability

High Known exploited NuGet
Severity
7.5 / 10
High · CVSS 3.0
Exploit chance (EPSS)
74.69%
Chance of exploitation in the next 30 days. Higher than 99.50% of scored vulnerabilities.
Known exploited
Yes
In CISA's catalog
Weakness
CWE-843 Access of Resource Using Incompatible Type ('Type Confusion')
Fix
1.10.1
Upgrade Microsoft.ChakraCore to this version or later

Description

A remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka "Scripting Engine Memory Corruption Vulnerability." This affects ChakraCore. This CVE ID is unique from CVE-2018-8242, CVE-2018-8283, CVE-2018-8287, CVE-2018-8288, CVE-2018-8291, CVE-2018-8296.

Affected versions

NuGet

PackageVulnerableFixed in
Microsoft.ChakraCore
< 1.10.1
1.10.1
Microsoft.ChakraCore
< 1.10.1
1.10.1

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

Microsoft.ChakraCore NuGet → 1.10.1

dotnet
dotnet add package Microsoft.ChakraCore --version 1.10.1

Severity breakdown

CVSS 3.0 7.5

CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H/E:H

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
Exploit maturity
H

Weakness

CWE-843: Access of Resource Using Incompatible Type ('Type Confusion')

The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.

References

Timeline

  1. Published
  2. Last updated by the source
AdvisorySeverityWhy it's related
GHSA-5whg-j5fv-xcm2
ChakraCore RCE Vulnerability
High Known exploited Also affects Microsoft.ChakraCore
GHSA-4f5g-j7wg-7w8j
ChakraCore RCE Vulnerability
High Known exploited Also affects Microsoft.ChakraCore
GHSA-vvvh-5xrm-pxff
ChakraCore information disclosure vulnerability
High Also affects Microsoft.ChakraCore
GHSA-v8jw-x9wq-hw4v
Chakra Scripting Engine RCE via Out-of-bounds write
High Also affects Microsoft.ChakraCore
GHSA-g8q3-rcf9-qx4q
Chakra Scripting Engine RCE Vulnerability
High Also affects Microsoft.ChakraCore
GHSA-fxrx-5j36-pwg5
Chakra Scripting Engine RCE via Out-of-bounds write
High Also affects Microsoft.ChakraCore
GHSA-4v6q-gjm6-6vv4
ChakraCore RCE via Out-of-bounds write
High Also affects Microsoft.ChakraCore
GHSA-jgrp-6qqq-3284
Chakra Scripting Engine and ChakraCore Vulnerable to Memory Corruption
High Also affects Microsoft.ChakraCore
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor