# CVE-2017-0218: Security feature bypass in Microsoft Windows

> Attackers can bypass Device Guard code integrity to inject malicious code into PowerShell sessions on Windows 10 and Server 2016.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-ffhm-frg4-m7jm

## What is CVE-2017-0218?

CVE-2017-0218 is a medium-severity vulnerability in Microsoft Windows 10, published on 15 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Microsoft Windows 10 Gold, Windows 10 1511, Windows 10 1607, and Windows Server 2016 allow an attacker to exploit a security feature bypass vulnerability in Device Guard that could allow the attacker to inject malicious code into a Windows PowerShell session, aka "Device Guard Code Integrity Policy Security Feature Bypass Vulnerability." This CVE ID is unique from CVE-2017-0173, CVE-2017-0215, CVE-2017-0216, and CVE-2017-0219.

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

It affects 2 products.


Products: Microsoft Windows 10, Microsoft Windows Server 2016.

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

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

## Is CVE-2017-0218 being exploited?

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

## Other vulnerabilities in Microsoft Windows 10

- [CVE-2015-2426](https://insights.sbomify.com/CVE-2015-2426/): Microsoft Windows Adobe Type Manager Library Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2015-1769](https://insights.sbomify.com/CVE-2015-1769/): Microsoft Windows Mount Manager Privilege Escalation (medium 6.6, exploited in the wild)
- [CVE-2020-1467](https://insights.sbomify.com/CVE-2020-1467/): Windows Hard Link Elevation of Privilege Vulnerability (critical 10.0)
- [CVE-2021-26424](https://insights.sbomify.com/CVE-2021-26424/): Windows TCP/IP Remote Code Execution Vulnerability (critical 9.9)
- [CVE-2021-28476](https://insights.sbomify.com/CVE-2021-28476/): Windows Hyper-V Remote Code Execution Vulnerability (critical 9.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-0218 is a medium-severity vulnerability in Microsoft Windows 10, published on 15 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-0218 in the wild and no public exploit code.

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

## Sources

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

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