Skip to content

GHSA-5hxp-3237-j2hp CVE-2018-8139

ChakraCore RCE Vulnerability

High NuGet
Severity
7.5 / 10
High · CVSS 3.0
Exploit chance (EPSS)
66.31%
Chance of exploitation in the next 30 days. Higher than 99.28% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-125 Out-of-bounds Read
Fix
1.8.4
Upgrade Microsoft.ChakraCore to this version or later

Description

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 affects Microsoft Edge, ChakraCore. This CVE ID is unique from CVE-2018-0945, CVE-2018-0946, CVE-2018-0951, CVE-2018-0953, CVE-2018-0954, CVE-2018-0955, CVE-2018-1022, CVE-2018-8114, CVE-2018-8122, CVE-2018-8128, CVE-2018-8137.

Affected versions

NuGet

PackageVulnerableFixed in
Microsoft.ChakraCore
< 1.8.4
1.8.4

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.8.4

dotnet
dotnet add package Microsoft.ChakraCore --version 1.8.4

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

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

Weakness

CWE-125: Out-of-bounds Read

The product reads data past the end, or before the beginning, of the intended buffer.

How to prevent it
  • Implementation: Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright. To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.
  • Architecture and Design: Use a language that provides appropriate memory abstractions.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
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
CVE-2018-8298
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
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