# CVE-2018-8415: Code injection in PowerShell Core

> Attackers can execute unlogged code in PowerShell, bypassing security controls and potentially compromising Windows systems.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 14 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-69m5-86x3-v3m5

## What is CVE-2018-8415?

CVE-2018-8415 is a high-severity code injection vulnerability in Microsoft Windows 10, published on 14 Nov 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A tampering vulnerability exists in PowerShell that could allow an attacker to execute unlogged code, aka "Microsoft PowerShell Tampering Vulnerability." This affects Windows 7, PowerShell Core 6.1, Windows Server 2012 R2, Windows RT 8.1, PowerShell Core 6.0, Windows Server 2019, Windows Server 2012, Windows 8.1, Windows Server 2016, Windows Server 2008 R2, Windows 10, Windows 10 Servers.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 9 products.


Products: Microsoft Powershell Core, Microsoft Windows 10, Microsoft Windows 7, Microsoft Windows 8.1, Microsoft Windows Rt 8.1, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019.

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

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

## Is CVE-2018-8415 being exploited?

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

## Other vulnerabilities in Microsoft Windows 10

- [CVE-2019-0627](https://insights.sbomify.com/CVE-2019-0627/): Security feature bypass in PowerShell Core (high 7.8)
- [CVE-2019-0631](https://insights.sbomify.com/CVE-2019-0631/): Security feature bypass in PowerShell Core (high 7.8)
- [CVE-2019-0632](https://insights.sbomify.com/CVE-2019-0632/): Security feature bypass in PowerShell Core (high 7.8)
- [CVE-2019-1167](https://insights.sbomify.com/CVE-2019-1167/): System.Management.Automation subject to bypass via script debugging (medium 4.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-8415 and fix it if it is affected.

What it is: CVE-2018-8415 is a high-severity code injection vulnerability in Microsoft Windows 10, published on 14 Nov 2018. 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-2018-8415 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-2018-8415/ (Markdown: https://insights.sbomify.com/CVE-2018-8415/index.md)
```

## Sources

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

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