Microsoft Office
CVE-2017-0199
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconDeliver weaponized RTF document via email
-
DeliveryUser opens document
-
ExploitOffice processes embedded OLE object
-
InstallRetrieve remote HTA payload via HTTP
-
C2Execute HTA script in user context
-
ExecuteInstall malware or establish C2
-
ImpactEscalate privileges or move laterally
Vulnerability Assessment
| Exploitation Conditions | User interaction required - victim must open the malicious RTF or Office document (DOC, DOCX formats confirmed vulnerable per exploit analyses). No special Office configuration, macro enabling, or Protected View bypass required, distinguishing this from typical macro-based attacks. Exploitation succeeds against default Office installations without security warnings because OLE object handling predates macro security controls. Requires outbound HTTP/HTTPS connectivity from victim workstation to attacker-controlled server hosting the HTA payload; network egress filtering to unknown external domains limits but does not prevent exploitation if attacker uses compromised legitimate sites. All Office versions 2007-2016 on all supported Windows platforms vulnerable in default configuration. User privilege level (standard vs. administrator) does not prevent initial exploitation but limits post-exploitation impact per CVSS privileges required: none (PR:N). |
| Impact | This represents critical real-world risk despite apparent CVSS inconsistencies. CISA KEV status confirms active exploitation in the wild, corroborated by the extraordinary EPSS score of 94.33% (100th percentile), indicating widespread attacker interest and deployment. Multiple detailed POC exploits exist including automated RTF weaponization tools documented by FireEye, MDSec, and NVISO. The attack requires only user interaction (UI:R) to open a document - a low barrier easily achieved through phishing campaigns. The CVSS vector shows AV:L which conflicts with the remote delivery mechanism described in exploit analyses; this likely reflects Microsoft's assessment that code executes in local user context after document opening, but defenders should treat this as a remote threat vector. No privileges required (PR:N) means any user opening the document triggers exploitation. The combination of KEV listing, near-perfect EPSS score, public exploit tooling, and low exploitation complexity make this an immediate patching priority regardless of the 7.8 CVSS score. The vulnerability's age (2017) and continued KEV presence suggest persistent exploitation of unpatched legacy systems. |
| Exploit ScenarioDerived | Attacker crafts malicious RTF or Office document embedding an OLE object that references remote HTA payload hosted on attacker-controlled server. Document delivered via phishing email with social engineering lure prompting user to open attachment. Upon opening, Office invokes Windows API to process embedded object, triggering HTTP request to retrieve and execute HTA file containing malicious script or executable payload, granting attacker code execution in user context with full user privileges. Public POCs from Exploit-DB (41894, 41934) and detailed exploitation guides from FireEye and MDSec enable rapid weaponization. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Apr 22, 2026
Remote code execution in Microsoft Office 2007-2016 and Windows Vista through 10 allows attackers to execute arbitrary code via malicious RTF or Office documents exploiting Windows API object linking. Confirmed actively exploited (CISA KEV) with EPSS score of 94.33% indicating near-certain real-world exploitation probability. Multiple public exploit codes available including weaponized RTF generators. Despite local attack vector classification (AV:L), exploitation occurs remotely through email/web delivery of crafted documents requiring only user interaction to open the file.
Earlier versions of this analysis (1)
A remote code execution vulnerability in Microsoft Office/WordPad's handling of OLE objects through the Windows API enables attackers to execute code via crafted documents, becoming one of the most widely exploited Office vulnerabilities of 2017-2019.
RemediationAI
Apply vendor-released security updates immediately from Microsoft Security Update Guide (https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-0199). Microsoft released patches in April 2017 addressing all affected Office and Windows versions. For systems unable to patch immediately, implement compensating controls: disable the Windows HTA handler by modifying registry key HKEY_CLASSES_ROOT\htafile\Shell\Open\Command (note: breaks legitimate HTA applications used by IT departments). Configure Office Trust Center to block activation of all OLE packages and embedded objects via Group Policy setting 'Packager Activation' to 'Enabled: Prompt User' or 'Enabled: Disable' (trade-off: may break legitimate documents with embedded objects). Deploy email gateway filtering to block RTF attachments and Office documents with embedded OLE objects from external sources (side effect: blocks some legitimate business documents). For Philips IntelliSpace Portal 7.0 users, consult https://ics-cert.us-cert.gov/advisories/ICSMA-18-058-02 for medical device-specific guidance. Given active exploitation status, prioritize patching over workarounds.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This vulnerability exploits the Windows Object Linking and Embedding (OLE) mechanism, specifically the HTA (HTML Application) handler invoked when Office applications process specially crafted RTF or Office documents. Affected products span Microsoft Office 2007 SP3, 2010 SP2, 2013 SP1, and 2016, as well as WordPad on Windows Vista SP2, Server 2008 SP2, Windows 7 SP1, Windows 8.1, Server 2008 R2 SP1, and Server 2012. The CPE data reveals extended impact including Philips IntelliSpace Portal 7.0 medical imaging software. The attack leverages improper validation of embedded objects, allowing remote content retrieval and execution through the Windows API without triggering standard macro security warnings. The CVSS vector classification of AV:L appears inconsistent with exploitation methodology which involves remote delivery of malicious documents, suggesting the local vector refers to code execution context rather than attack delivery method.
Know when Office gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
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
Lifecycle Timeline
5DescriptionCVE.org
Microsoft Office 2007 SP3, Microsoft Office 2010 SP2, Microsoft Office 2013 SP1, Microsoft Office 2016, Microsoft Windows Vista SP2, Windows Server 2008 SP2, Windows 7 SP1, Windows 8.1 allow remote attackers to execute arbitrary code via a crafted document, aka "Microsoft Office/WordPad Remote Code Execution Vulnerability w/Windows API."
Executive ViewAI
CVE-2017-0199 is a critical remote code execution vulnerability affecting Microsoft Office 2007-2016 that enables attackers to execute arbitrary code through malicious documents delivered via email or web, requiring only user interaction to trigger. This vulnerability is confirmed actively exploited (CISA KEV) with a 94.3% exploitation probability, presenting immediate risk to any organization using affected Office versions. Urgent patching is required to prevent compromise of endpoints and potential lateral movement into corporate networks.
Apply vendor patch. Interim mitigations if patch deployment delayed: disable RTF file handling in Office via registry; block RTF and suspicious Office file types (.docx, .rtf) at email gateway; restrict Office macro execution through Group Policy; isolate vulnerable systems from network if patching cannot be completed within 48 hours.
Threat Intelligence Overview
NVD
CVE.org
CISA KEV
EPSS
Exploit-DB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Affected Products (CPE)CVE.org
Microsoft Word Remote Code Execution Vulnerability. Rated critical severity (CVSS 9.8), this vulnerability is remotely e
Microsoft SharePoint Server 2007 SP3, 2010 SP1 and SP2, and 2013; Office Web Apps 2010; Excel 2003 SP3, 2007 SP3, 2010 S
The font library in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows
Microsoft Word 2007 SP3, Office 2010 SP2, Word 2010 SP2, Word 2013 SP1, Word 2013 RT SP1, Office for Mac 2011, Office fo
Microsoft Word 2007 SP3, Office 2010 SP2, Word 2010 SP2, Word Automation Services in SharePoint Server 2010, Web Applica
Buffer overflow in the Adobe Type Manager Library in Microsoft Windows Vista SP2, Windows Server 2008 SP2, Office 2007 S
Microsoft Word 2007 SP3, Office 2010 SP2, Word 2010 SP2, and Office for Mac 2011 allow remote attackers to execute arbit
Microsoft Office 2007 SP3 allows remote attackers to execute arbitrary code via a crafted document, aka "Microsoft Offic
Integer underflow in Microsoft Office 2007 SP3, Office 2010 SP2, Office 2013 SP1, Office 2013 RT SP1, Office for Mac 201
Microsoft Office 2007 SP3 and 2010 SP2, Live Meeting 2007 Console, Lync 2010, Lync 2010 Attendee, Lync 2013 SP1, and Lyn
Microsoft Excel Security Feature Bypass Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authenti
Uniscribe in Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT
GitHub PoC