# CVE-2017-11767: ChakraCore vulnerable to privilege escalation

> An attacker can execute arbitrary code with current user privileges due to memory corruption in the ChakraCore scripting engine.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Nov 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-c79v-2rjq-965m

## What is CVE-2017-11767?

CVE-2017-11767 is a critical memory corruption vulnerability in Microsoft Chakracore, published on 2 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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, aka "Scripting Engine Memory Corruption Vulnerability".

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2017-11767?

2 open source packages ship an affected version, including Microsoft.ChakraCore. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Microsoft.ChakraCore` | NuGet | All versions | 1.6.2 |
| `Microsoft.ChakraCore` | NuGet | All versions | 1.6.2 |

Products: Microsoft Chakracore.

## How do I fix CVE-2017-11767?

Upgrade Microsoft.ChakraCore to 1.6.2 or later.

## Is CVE-2017-11767 being exploited?

There is no known exploitation of CVE-2017-11767 in the wild and no public exploit code.

## Other vulnerabilities in Microsoft Chakracore

- [CVE-2018-8298](https://insights.sbomify.com/CVE-2018-8298/): ChakraCore Scripting Engine Type Confusion (high 7.5, exploited in the wild)
- [CVE-2020-0878](https://insights.sbomify.com/CVE-2020-0878/): Microsoft Edge and Internet Explorer Memory Corruption (medium 4.2, exploited in the wild)
- [CVE-2018-8500](https://insights.sbomify.com/CVE-2018-8500/): ChakraCore RCE Vulnerability (critical 9.8)
- [CVE-2017-8658](https://insights.sbomify.com/CVE-2017-8658/): ChakraCore RCE Vulnerability (critical 9.8)
- [CVE-2020-1555](https://insights.sbomify.com/CVE-2020-1555/): Scripting Engine Memory Corruption Vulnerability (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-11767 and fix it if it is affected.

What it is: CVE-2017-11767 is a critical memory corruption vulnerability in Microsoft Chakracore, published on 2 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-11767 in the wild and no public exploit code.

Affected packages and fixed versions:
- Microsoft.ChakraCore (NuGet): affected all versions; fixed in 1.6.2
- Microsoft.ChakraCore (NuGet): affected all versions; fixed in 1.6.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-11767/ (Markdown: https://insights.sbomify.com/CVE-2017-11767/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-11767
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-11767
- OSV: https://osv.dev/vulnerability/CVE-2017-11767

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-11767/
Summaries are generated and may contain mistakes; the official description above is the record.