# CVE-2017-8659: ChakraCore information disclosure vulnerability

> An attacker can obtain sensitive memory information from Microsoft Edge via the Chakra scripting engine, aiding further system compromise.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **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:** 8 Aug 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-h6m7-jphx-f9p5

## What is CVE-2017-8659?

CVE-2017-8659 is a medium-severity vulnerability in Microsoft Edge, published on 8 Aug 2017. 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 Edge in Microsoft Windows 10 1703 allows an attacker to obtain information to further compromise the user's system due to the Chakra scripting engine not properly handling objects in memory, aka "Scripting Engine Information Disclosure Vulnerability".

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

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.1 |
| `Microsoft.ChakraCore` | NuGet | All versions | 1.6.1 |

Products: Microsoft Edge.

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

Upgrade Microsoft.ChakraCore to 1.6.1 or later.

## Is CVE-2017-8659 being exploited?

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

## Other vulnerabilities in Microsoft Edge

- [CVE-2021-26411](https://insights.sbomify.com/CVE-2021-26411/): Microsoft Internet Explorer Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2016-7200](https://insights.sbomify.com/CVE-2016-7200/): Microsoft Edge Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2016-7201](https://insights.sbomify.com/CVE-2016-7201/): Microsoft Edge Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2017-0037](https://insights.sbomify.com/CVE-2017-0037/): Microsoft Edge and Internet Explorer Type Confusion (high 8.1, exploited in the wild)
- [CVE-2016-3351](https://insights.sbomify.com/CVE-2016-3351/): Microsoft Internet Explorer and Edge Information Disclosure (medium 6.5, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8659 is a medium-severity vulnerability in Microsoft Edge, published on 8 Aug 2017. 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-2017-8659 in the wild and no public exploit code.

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

## Sources

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

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