Security readout for executives and security teams
Plain-English summary
This vulnerability lets an attacker run code when a user opens a malicious document or application on a system with affected Microsoft .NET Framework versions. It is not purely remote without user interaction, but successful exploitation can fully compromise confidentiality, integrity, and availability.
Executive priority
Prioritize this as an urgent legacy Windows exposure. KEV status means exploitation has been observed, and the impact can be full host compromise after user interaction. Patch validation should be tracked to completion.
Technical view
CVE-2017-8759 is a .NET Framework remote code execution vulnerability classified as CWE-94. The CVSS vector shows local attack vector, low complexity, no privileges, and required user interaction, with high impact across confidentiality, integrity, and availability.
Likely exposure
Exposure is likely on Windows systems running Microsoft .NET Framework 2.0, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, or 4.7, especially where users open external documents or applications.
Exploitation context
Active exploitation is supported by CISA KEV listing. Public exploit references also exist, but this assessment does not rely on or describe exploitation mechanics. The strongest business concern is user-driven compromise through malicious content.
Researcher notes
Evidence identifies affected .NET Framework versions, RCE impact, public exploit references, and KEV status. The bundle does not provide safe technical root-cause detail or complete environmental prerequisites, so validation should be advisory- and scanner-driven.
Mitigation direction
- Apply Microsoft security updates for CVE-2017-8759 using MSRC guidance.
- Inventory hosts with affected .NET Framework versions.
- Prioritize remediation for user workstations and document-processing systems.
- Restrict untrusted documents and applications where patching is delayed.
- Monitor vendor guidance for unsupported platform constraints.
Validation and detection
- Confirm affected .NET Framework versions are absent or patched.
- Check vulnerability scanner results against Microsoft advisory coverage.
- Review CISA KEV tracking for remediation obligations.
- Validate endpoint controls detect suspicious document-launched child processes.
- Confirm users handling external files are in the patched population.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2017-8759 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CISA KEV status
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/bhdresh/CVE-2017-8759CVE reference · x_refsource_MISC
- https://github.com/nccgroup/CVE-2017-8759CVE reference · x_refsource_MISC
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-8759CVE reference · x_refsource_CONFIRM
- 42711CVE reference · exploit, x_refsource_EXPLOIT-DB
- https://github.com/GitHubAssessments/CVE_Assessments_01_2020CVE reference · x_refsource_MISC
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2017-8759CVE reference · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.