# CVE-2017-8759: Microsoft .NET Framework Remote Code Execution

> Remote attackers can execute arbitrary code via malicious documents or applications exploiting a code injection flaw in the .NET Framework.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Sep 2017
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-rc4w-p9f6-7c7q

## What is CVE-2017-8759?

CVE-2017-8759 is a high-severity code injection vulnerability in Microsoft .Net Framework, published on 13 Sep 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Microsoft .NET Framework 2.0, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2 and 4.7 allow an attacker to execute code remotely via a malicious document or application, aka ".NET Framework Remote Code Execution Vulnerability."

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

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

It affects 1 product.


Products: Microsoft .Net Framework.

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

No fix has been published for CVE-2017-8759 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2017-8759 being exploited?

Yes. Attackers have exploited CVE-2017-8759 in the wild since at least 3 Nov 2021.

Public exploit code:

- Exploit toolkit CVE-2017-8759 - v1.0 is a handy python script which provides pentesters and security researchers a quick and effective way to test Microsoft .NET Framework RCE. It could generate a malicious RTF file and deliver metasploit / meterpreter / other payload to victim without any complex configuration. (github_poc): https://github.com/bhdresh/CVE-2017-8759
- Running CVE-2017-8759 exploit sample. (github_poc): https://github.com/Voulnet/CVE-2017-8759-Exploit-sample
- CVE-2017-8759 - A vulnerability in the SOAP WDSL parser. (github_poc): https://github.com/vysecurity/CVE-2017-8759
- NCC Group's analysis and exploitation of CVE-2017-8759 along with further refinements (github_poc): https://github.com/nccgroup/CVE-2017-8759
- Simple C# implementation of CVE-2017-8759 (github_poc): https://github.com/JonasUliana/CVE-2017-8759
- Two versions of CVE-2017-8759 exploits (github_poc): https://github.com/ashr/CVE-2017-8759-exploits

## Other vulnerabilities in Microsoft .Net Framework

- [CVE-2020-0646](https://insights.sbomify.com/CVE-2020-0646/): Microsoft .NET Framework Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2015-1671](https://insights.sbomify.com/CVE-2015-1671/): Microsoft Windows Remote Code Execution (high 7.8, exploited in the wild)
- [CVE-2024-29059](https://insights.sbomify.com/CVE-2024-29059/): Microsoft .NET Framework Information Disclosure (high 7.5, exploited in the wild)
- [CVE-2014-4073](https://insights.sbomify.com/CVE-2014-4073/): Privilege escalation in n/a (critical 10.0)
- [CVE-2014-4121](https://insights.sbomify.com/CVE-2014-4121/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8759 is a high-severity code injection vulnerability in Microsoft .Net Framework, published on 13 Sep 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2017-8759 in the wild since at least 3 Nov 2021.

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

## Sources

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

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