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

> A memory corruption vulnerability in Internet Explorer's scripting engine allows attackers to execute arbitrary code via specially crafted web content.

- **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-4gjj-326p-2q44

## What is CVE-2017-8618?

CVE-2017-8618 is a high-severity memory corruption vulnerability in Microsoft Internet Explorer, 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

Internet Explorer in Microsoft Windows 7 SP1, Windows Server 2008 R2 SP1, Windows 8.1 and Windows RT 8.1, Windows Server 2012 and R2, Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016 Internet Explorer in the way affected Microsoft scripting engines render when handling objects in memory, aka "Scripting Engine Memory Corruption Vulnerability." This CVE ID is unique from CVE-2017-8596, CVE-2017-8610, CVE-2017-8601, CVE-2017-8603, CVE-2017-8604, CVE-2017-8605, CVE-2017-8606, CVE-2017-8607, CVE-2017-8608, CVE-2017-8619, CVE-2017-9598 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-8618?

It affects 1 product.


Products: Microsoft Internet Explorer.

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

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

## Is CVE-2017-8618 being exploited?

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

Public exploit code:

- Microsoft Internet Explorer 11.1066.14393.0 - VBScript Arithmetic Functions Type Confusion (exploitdb)

## Other vulnerabilities in Microsoft Internet Explorer

- [CVE-2014-1776](https://insights.sbomify.com/CVE-2014-1776/): Microsoft Internet Explorer Memory Corruption (critical 9.8, exploited in the wild)
- [CVE-2021-27085](https://insights.sbomify.com/CVE-2021-27085/): Microsoft Internet Explorer Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2017-0222](https://insights.sbomify.com/CVE-2017-0222/): Microsoft Internet Explorer Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2017-0210](https://insights.sbomify.com/CVE-2017-0210/): Microsoft Internet Explorer Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2017-0149](https://insights.sbomify.com/CVE-2017-0149/): Microsoft Internet Explorer Memory Corruption (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8618 is a high-severity memory corruption vulnerability in Microsoft Internet Explorer, 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-8618 exists.

Affected product: Microsoft Internet Explorer. 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-8618/ (Markdown: https://insights.sbomify.com/CVE-2017-8618/index.md)
```

## Sources

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

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