CVE-2017-11908
ChakraCore RCE Vulnerability
Overview
Description
ChakraCore and Windows 10 1709 allows an attacker to execute arbitrary code in the context of the current user, due to how the scripting engine handles objects in memory, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-11886, CVE-2017-11889, CVE-2017-11890, CVE-2017-11893, CVE-2017-11894, CVE-2017-11895, CVE-2017-11901, CVE-2017-11903, CVE-2017-11905, CVE-2017-11905, CVE-2017-11907, CVE-2017-11909, CVE-2017-11910, CVE-2017-11911, CVE-2017-11912, CVE-2017-11913, CVE-2017-11914, CVE-2017-11916, CVE-2017-11918, and CVE-2017-11930.
Source: OX vulnerability database
Severity
7.5 · HIGH
CVSS 3.0 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Weakness: CWE-119
Affected packages · 1
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| NuGet | Microsoft.ChakraCore | <1.7.5 | 1.7.5 |
Open a package to see all its vulnerabilities.
Operating systems
No Linux distribution reports this ID.
References
- www.securityfocus.com http://www.securityfocus.com/bid/102052
- www.securitytracker.com http://www.securitytracker.com/id/1039990
- github.com https://github.com/chakra-core/ChakraCore/commit/39eecff7daecce96088f7ed737f145ee4774faa6
- github.com https://github.com/chakra-core/ChakraCore/pull/4411
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2017-11908
- portal.msrc.microsoft.com https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-11908
- web.archive.org https://web.archive.org/web/20210124122457/http://www.securityfocus.com/bid/102052
- web.archive.org https://web.archive.org/web/20210829201729/http://www.securitytracker.com/id/1039990
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.