Skip to content

GHSA-w3qr-8v4r-592m CVE-2018-8452

ChakraCore information disclosure vulnerability

Medium NuGet
Severity
4.3 / 10
Medium · CVSS 3.0
Exploit chance (EPSS)
5.59%
Chance of exploitation in the next 30 days. Higher than 92.89% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Fix
1.11.1
Upgrade Microsoft.ChakraCore to this version or later

Description

An information disclosure vulnerability exists when the scripting engine does not properly handle objects in memory in Microsoft browsers, aka "Scripting Engine Information Disclosure Vulnerability." This affects ChakraCore, Internet Explorer 11, Microsoft Edge.

Affected versions

NuGet

PackageVulnerableFixed in
Microsoft.ChakraCore
< 1.11.1
1.11.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.11.1

dotnet
dotnet add package Microsoft.ChakraCore --version 1.11.1

Severity breakdown

CVSS 3.0 4.3

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

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

Weakness

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How to prevent it
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

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