# CVE-2017-8606: Memory corruption in Microsoft Windows 7, Windows Server 2008 and R2, Windows 8.1 and Windows RT 8.1, Windows Server 2012 and R2, Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016

> Attackers can execute arbitrary code via memory corruption in Microsoft browsers' JavaScript engines when handling objects.

- **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:** No
- **Published:** 11 Jul 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-7v9x-9c2c-wxvx

## What is CVE-2017-8606?

CVE-2017-8606 is a high-severity memory corruption vulnerability in Microsoft Edge, published on 11 Jul 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 browsers in Microsoft Windows 7, Windows Server 2008 and R2, Windows 8.1 and Windows RT 8.1, Windows Server 2012 and R2, Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016 allow an attacker to execute arbitrary code in the context of the current user when the JavaScript engines fail to render when handling objects in memory in Microsoft browsers, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-8598, CVE-2017-8596, CVE-2017-8618, CVE-2017-8619, CVE-2017-8610, CVE-2017-8601, CVE-2017-8603, CVE-2017-8604, CVE-2017-8605, CVE-2017-8595, CVE-2017-8607, CVE-2017-8608, and CVE-2017-8609

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

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

It affects 2 products.


Products: Microsoft Edge, Microsoft Internet Explorer.

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

No fix has been published for CVE-2017-8606 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-8606 being exploited?

There is no known exploitation of CVE-2017-8606 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-8606 and fix it if it is affected.

What it is: CVE-2017-8606 is a high-severity memory corruption vulnerability in Microsoft Edge, published on 11 Jul 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-8606 in the wild and no public exploit code.

Affected product: Microsoft Edge. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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