Microsoft .NET Framework
CVE-2017-8759
HIGH
Severity by source
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Lifecycle Timeline
7DescriptionCVE.org
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."
AnalysisAI
Remote code execution in Microsoft .NET Framework versions 2.0 through 4.7 allows attackers to execute arbitrary code via malicious documents or applications. This vulnerability is confirmed actively exploited (CISA KEV) and carries an EPSS exploitation probability of 93.97% (100th percentile), indicating near-certain real-world targeting. Public exploit code is available from multiple sources including GitHub repositories. The attack requires local access and user interaction (opening a weaponized document), but no authentication, making it highly effective in phishing and watering hole campaigns.
Technical ContextAI
This vulnerability affects the Microsoft .NET Framework runtime environment, a software development platform for building and running Windows applications. The flaw is classified as CWE-94 (Code Injection), indicating that attacker-controlled code can be injected into the .NET Framework's execution context. The affected versions span legacy (.NET 2.0, 3.5, 3.5.1) to modern (.NET 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7) frameworks. The CPE data confirms impact across all these major version branches. The vulnerability leverages .NET's document processing capabilities to inject and execute malicious code, exploiting weaknesses in how the framework handles untrusted input from specially crafted files or applications.
RemediationAI
Apply Microsoft security updates immediately from the official MSRC advisory at https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-8759, which provides patches for all affected .NET Framework versions across supported Windows operating systems. Microsoft released these patches as part of the September 2017 security update cycle. Organizations should prioritize patching systems accessible to users who handle external documents or emails, as these are primary attack vectors. As a temporary compensating control until patching is complete, implement application whitelisting to prevent execution of untrusted applications, disable .NET SOAP processing if not required for business operations, and enforce email gateway filtering to block suspicious document attachments (particularly those invoking .NET components). User security awareness training should emphasize risks of opening unsolicited documents. Note that blocking specific file types provides only partial protection since the vulnerability can be triggered through multiple .NET-enabled document formats and applications.
Share
External POC / Exploit Code
Leaving vuln.today