# CVE-2018-0818: ChakraCore RCE Vulnerability

> Attackers can bypass Control Flow Guard in ChakraCore to execute arbitrary code when combined with another vulnerability.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 10 Jan 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-fv8m-p45w-gf38

## What is CVE-2018-0818?

CVE-2018-0818 is a high-severity vulnerability in Microsoft Chakracore, published on 10 Jan 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Microsoft ChakraCore allows an attacker to bypass Control Flow Guard (CFG) in conjunction with another vulnerability to run arbitrary code on a target system, due to how the Chakra scripting engine handles accessing memory, aka "Scripting Engine Security Feature Bypass".

## Which versions are affected by CVE-2018-0818?

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.8.0 |
| `Microsoft.ChakraCore` | NuGet | All versions | 1.8.0 |

Products: Microsoft Chakracore.

## How do I fix CVE-2018-0818?

Upgrade Microsoft.ChakraCore to 1.8.0 or later.

## Is CVE-2018-0818 being exploited?

There is no known exploitation of CVE-2018-0818 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-11767](https://insights.sbomify.com/CVE-2017-11767/): ChakraCore vulnerable to privilege escalation (critical 9.8)
- [CVE-2017-8658](https://insights.sbomify.com/CVE-2017-8658/): ChakraCore RCE Vulnerability (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-0818 and fix it if it is affected.

What it is: CVE-2018-0818 is a high-severity vulnerability in Microsoft Chakracore, published on 10 Jan 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-0818 in the wild and no public exploit code.

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

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-2018-0818/ (Markdown: https://insights.sbomify.com/CVE-2018-0818/index.md)
```

## Sources

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

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