GHSA-f8f9-q5hg-9c7q CVE-2017-11801
ChakraCore RCE Vulnerability
- Severity
- 7.5 / 10
- High · CVSS 3.0
- Exploit chance (EPSS)
- 5.80%
- Chance of exploitation in the next 30 days. Higher than 93.12% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Fix
1.7.3- Upgrade Microsoft.ChakraCore to this version or later
Description
ChakraCore allows an attacker to execute arbitrary code in the context of the current user, due to how the ChakraCore scripting engine handles objects in memory, aka "Scripting Engine Information Disclosure Vulnerability". This CVE ID is unique from CVE-2017-11792, CVE-2017-11793, CVE-2017-11796, CVE-2017-11797, CVE-2017-11798, CVE-2017-11799, CVE-2017-11800, CVE-2017-11802, CVE-2017-11804, CVE-2017-11805, CVE-2017-11806, CVE-2017-11807, CVE-2017-11808, CVE-2017-11809, CVE-2017-11810, CVE-2017-11811, CVE-2017-11812, and CVE-2017-11821.
Affected versions
NuGet
| Package | Vulnerable | Fixed in |
|---|---|---|
| Microsoft.ChakraCore | < 1.7.3 |
1.7.3 |
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.7.3
- dotnet
dotnet add package Microsoft.ChakraCore --version 1.7.3
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-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
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why 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 |
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