# CVE-2018-8291: ChakraCore RCE Vulnerability

> Remote attackers can execute arbitrary code via memory corruption in the Microsoft scripting engine used by Edge and Internet Explorer.

- **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:** 11 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j67m-wpv6-pv44

## What is CVE-2018-8291?

CVE-2018-8291 is a high-severity memory corruption vulnerability in Microsoft Chakracore, published on 11 Jul 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

A remote code execution vulnerability exists in the way the scripting engine handles objects in memory in Microsoft browsers, aka "Scripting Engine Memory Corruption Vulnerability." This affects ChakraCore, Internet Explorer 11, Microsoft Edge. This CVE ID is unique from CVE-2018-8242, CVE-2018-8283, CVE-2018-8287, CVE-2018-8288, CVE-2018-8296, CVE-2018-8298.

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

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

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


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

Products: Microsoft Chakracore, Microsoft Edge, Microsoft Internet Explorer.

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

Upgrade Microsoft.ChakraCore to 1.10.1 or later.

## Is CVE-2018-8291 being exploited?

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

Public exploit code:

- Microsoft Edge Chakra JIT - 'DictionaryPropertyDescriptor::CopyFrom' Type Confusion (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-8291 and fix it if it is affected.

What it is: CVE-2018-8291 is a high-severity memory corruption vulnerability in Microsoft Chakracore, published on 11 Jul 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-8291 exists.

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

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

## Sources

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

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