dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 May 2022.
.net FrameworkApplication · Microsoft

CVE-2017-8759

HIGH · 7.8 CVSS v3.1 Published 2017-09-13
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
97/100
Remediation priority · Urgent
In the wild High EPSS Public exploit No privileges Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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."

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

CVE-2017-8759 is a remote code execution vulnerability in Microsoft .NET Framework versions 2.0 through 4.7, caused by improper parsing of SOAP WSDL (Web Services Description Language) content. Attackers exploit this vulnerability by tricking users into opening malicious documents or applications that trigger the flawed parsing, allowing arbitrary code execution on the targeted system.

MitigationApply Microsoft security updates (KB 4039094 and subsequent cumulative updates) to all systems running affected .NET Framework versions, and educate users about the risks of opening unexpected documents from untrusted sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
.net FrameworkApplication
Affected:= 4.5.2= 3.5.1= 3.5= 2.0= 4.6.1= 4.6= 4.7= 4.6.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed .NET Framework version
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full (for .NET 4.x) or HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5, v3.0, v2.0 for older versions. Check the Version value in each subkey.
    Affected if The Version value matches 2.0, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, or 4.7, or falls within the 2.0 through 4.7 range.
  2. Check .NET version via command line
    Run "reg query \"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\" /v Version" in Command Prompt to query .NET 4.x version. For older versions, query the respective subkeys under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\.
    Affected if The reported version falls within or matches any of the affected versions 2.0 through 4.7.
  3. Verify security update KB 4039094 is installed
    Open Control Panel > Programs and Features > View installed updates, or run "wmic qfe get hotfixid" in Command Prompt, and search for KB4039094 or later cumulative updates.
    Affected if KB4039094 or a subsequent cumulative update is NOT installed on the system.
  4. Check if vulnerable WSDL parsing component is present
    Verify the presence of System.Runtime.Remoting.dll and related WSDL parsing components in the .NET Framework installation directory (typically C:\Windows\Microsoft.NET\Framework\v* or C:\Windows\Microsoft.NET\Framework64\v*).
    Affected if The .NET Framework is installed with the vulnerable version range and the WSDL parsing components exist on the system.

A system is affected if it runs any .NET Framework version from 2.0 through 4.7 without the KB4039094 or later security updates installed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch portal.msrc.microsoft.com →
Interim mitigation

Apply Microsoft security updates (KB 4039094 and subsequent cumulative updates) to all systems running affected .NET Framework versions, and educate users about the risks of opening unexpected documents from untrusted sources.

Recommended fix High confidence
  1. Check installed .NET Framework version by inspecting the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client (or Full) for the Version value
  2. Open Windows Update or Microsoft Update Catalog
  3. Search for and install the relevant security update for this vulnerability (Microsoft Security Bulletin MS17-013, or September 2017 Cumulative Security Update for .NET Framework)
  4. Alternatively, manually download the specific KB from the Microsoft Update Catalog matching your Windows and .NET version
  5. Restart the system after applying the update
  6. Verify the update was successfully installed by checking Add/Remove Programs for the installed update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in .net Framework Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-8759 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-8759 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data