# CVE-2018-0934: ChakraCore RCE Vulnerability

> Remote attackers can execute arbitrary code by exploiting a memory corruption flaw in the Chakra scripting engine within Windows and Edge.

- **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:** 14 Mar 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-phcc-frh9-q545

## What is CVE-2018-0934?

CVE-2018-0934 is a high-severity memory corruption vulnerability in Microsoft Chakracore, published on 14 Mar 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

ChakraCore and Microsoft Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows Server 2016 allows remote code execution, due to how the Chakra scripting engine handles objects in memory, aka "Chakra Scripting Engine Memory Corruption Vulnerability". This CVE ID is unique from CVE-2018-0872, CVE-2018-0873, CVE-2018-0874, CVE-2018-0930, CVE-2018-0931, CVE-2018-0933, CVE-2018-0936, and CVE-2018-0937.

Weakness: CWE-787 (Out-of-bounds Write), CWE-755 (Improper Handling of Exceptional Conditions)

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

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


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

Products: Microsoft Chakracore, Microsoft Edge.

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

Upgrade Microsoft.ChakraCore to 1.8.2 or later.

## Is CVE-2018-0934 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-0934 exists.

Public exploit code:

- Microsoft Edge Chakra JIT - Stack-to-Heap Copy (Incomplete Fix) (1) (exploitdb)
- Microsoft Edge Chakra JIT - Stack-to-Heap Copy (Incomplete Fix) (2) (exploitdb)

## 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-0934 and fix it if it is affected.

What it is: CVE-2018-0934 is a high-severity memory corruption vulnerability in Microsoft Chakracore, published on 14 Mar 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-0934 exists.

Affected packages and fixed versions:
- Microsoft.ChakraCore (NuGet): affected all versions; fixed in 1.8.2
- Microsoft.ChakraCore (NuGet): affected all versions; fixed in 1.8.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-2018-0934/ (Markdown: https://insights.sbomify.com/CVE-2018-0934/index.md)
```

## Sources

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

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