GHSA-c79v-2rjq-965m CVE-2017-11767
ChakraCore vulnerable to privilege escalation
Critical
NuGet
- Severity
- 9.8 / 10
- Critical · CVSS 3.0
- Exploit chance (EPSS)
- 9.51%
- Chance of exploitation in the next 30 days. Higher than 95.45% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
- Fix
1.6.2- Upgrade Microsoft.ChakraCore to this version or later
Description
ChakraCore allows an attacker to gain the same user rights as the current user, due to the way that the ChakraCore scripting engine handles objects in memory. If the current user is logged on with administrative user rights, an attacker who successfully exploited the vulnerability could take control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
Affected versions
NuGet
| Package | Vulnerable | Fixed in |
|---|---|---|
| Microsoft.ChakraCore | < 1.6.2 |
1.6.2 |
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.6.2
- dotnet
dotnet add package Microsoft.ChakraCore --version 1.6.2
Severity breakdown
CVSS 3.0 9.8
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Weakness
CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
How to prevent it
- Requirements: Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega [REF-57], and the Strsafe.h library from Microsoft [REF-56]. These libraries provide safer versions of overflow-prone string-handling functions.
- Operation, Build and Compilation: Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
- Implementation: Consider adhering to the following rules when allocating and managing an application's memory: Double check that the buffer is as large as specified. When using functions that accept a number of bytes to copy, such as strncpy(), be aware that if the destination buffer size is equal to the source buffer size, it may not NULL-terminate the string. Check buffer boundaries if accessing the buffer in a loop and make sure there is no danger of writing past the allocated space. If necessary, truncate all input strings to a reasonable length before passing them to the copy and concatenation functions.
- Operation, Build and Compilation: Run or compile the software using features or extensions that randomly arrange the positions of a program's executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code. Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as "rebasing" (for Windows) and "prelinking" (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking. For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].
- Operation: Use a CPU and operating system that offers Data Execution Protection (using hardware NX or XD bits) or the equivalent techniques that simulate this feature in software, such as PaX [REF-60] [REF-61]. These techniques ensure that any instruction executed is exclusively at a memory address that is part of the code segment. For more information on these techniques see D3-PSEP (Process Segment Execution Prevention) from D3FEND [REF-1336].
- Implementation: Replace unbounded copy functions with analogous functions that support length arguments, such as strcpy with strncpy. Create these if they are not available.
References
Advisories
Packages
Other links
- github.com/chakra-core/ChakraCore/pull/3727
- github.com/chakra-core/ChakraCore/pull/3727/commits/b3e3959d14814f42ee2197c504c…
- github.com/chakra-core/ChakraCore/commit/b3e3959d14814f42ee2197c504c322bcbe12347d
- msrc.microsoft.com/update-guide/en-US/advisory/CVE-2017-11767
- web.archive.org/web/20210124103810/http://www.securityfocus.com/bid/100838
- web.archive.org/web/20211127230635/http://www.securitytracker.com/id/1039369
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