Skip to main content
Mallory
HighCISA KEVExploited in the wildPublic exploit

Microsoft Office/WordPad Remote Code Execution Vulnerability

IdentifiersCVE-2017-0199CWE-94

CVE-2017-0199 is a remote code execution vulnerability affecting Microsoft Office 2007 SP3, Office 2010 SP2, Office 2013 SP1, Office 2016, and supported Windows components including WordPad on Windows Vista SP2, Windows Server 2008 SP2, Windows 7 SP1, and Windows 8.1. The vulnerability is triggered when a user opens or otherwise renders a crafted Office or RTF document that abuses OLE/remote template handling to retrieve attacker-controlled content from an external source. Multiple reports in the provided content describe malicious DOCX/RTF documents using an OLE object or remote template injection to fetch a remote RTF or template, which can then execute script or follow-on exploit content, including Visual Basic script with PowerShell commands. The issue was widely weaponized in phishing campaigns and commonly used as an initial access vector to deliver malware such as Dridex, FINSPY, LATENTBOT, Agent Tesla, Ande Loader, SmokeLoader, and SideWinder payloads.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote attackers to execute arbitrary code on the victim system in the context of the current user and, as described in the supporting content, effectively take control of the system. In observed campaigns, exploitation was used to download and launch secondary payloads, install banking trojans and information stealers, execute PowerShell or HTA-based loaders, and establish broader compromise for espionage or financially motivated malware deployment. Depending on user privileges and post-exploitation tooling, this can lead to malware installation, credential theft, persistence, lateral movement, and full host compromise.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by blocking or tightly controlling delivery of Office, RTF, and template-bearing documents from untrusted sources; harden email filtering against phishing attachments and links; restrict outbound retrieval of remote templates/content from Office applications; use Protected View and related document-origin protections; train users not to open unsolicited attachments or click 'Enable Editing' on untrusted files; and monitor for child-process execution and LOLBin activity from Office applications, including PowerShell, mshta.exe, and similar follow-on execution paths. Additional compensating controls include endpoint protection, attachment sandboxing, network egress monitoring, and detection content for CVE-2017-0199-related document behavior.

Remediation

Patch, then assume compromise.

Apply Microsoft's security updates released for CVE-2017-0199, including the April 11, 2017 patch cycle referenced in the content, to all affected Microsoft Office and Windows/WordPad installations. Prioritize patching legacy Office deployments and unsupported or slow-to-update systems that continue to be targeted in phishing campaigns. Organizations should also retire end-of-life software where possible and verify that all Office and Windows components handling OLE and RTF content are updated to vendor-fixed versions.
PUBLIC EXPLOITS

Exploits

6 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (8 hidden).

VALID 6 / 14 TOTALView more in app
RCE-CVE-2017-0199-detection-analysisMaturityPoCVerified exploit

Repository contains a single malicious Microsoft Word DOCX sample (OpenXML structure) and a blue-team writeup. The exploit targets CVE-2017-0199 (Office/Word remote code execution via external template/HTA retrieval). The key exploit primitive is in word/_rels/settings.xml.rels: an attachedTemplate relationship with TargetMode="External" pointing to tt.vg at path /BVhaS (formatted as http://<username>@tt.vg/BVhaS). When opened, Word (WINWORD.EXE) attempts HTTP/HTTPS requests (GET/HEAD /BVhaS, OPTIONS /) to tt.vg; the README reports 404 responses in the sandbox run, implying the second-stage payload was unavailable at detonation time. Structure/purpose: - README.md: detailed sandbox detonation report (ANY.RUN) including attack chain narrative, network IOCs (tt.vg, /BVhaS, resolved IPs), and forensic artifacts (temp files, Content.MSO EMF cache) plus registry access notes and hunting query examples. - OpenXML parts: [Content_Types].xml, docProps/*, word/document.xml, word/settings.xml, and relationship files. The relationships show embedded OLE objects (AcroExch.Document.DC) and the external attachedTemplate pointer that drives the CVE-2017-0199 behavior. Overall, this is not a traditional exploit codebase but a weaponized document sample plus analysis. It provides a reproducible indicator set (domain/URL/IPs and artifact locations) and demonstrates how the DOCX is wired to trigger outbound retrieval that can lead to RCE on vulnerable Office installations.

ahmed-tarek22752Disclosed Nov 23, 2025xmlmarkdownclient-side / phishing document (malicious DOCX) triggering Office external template fetch leading to RCE (CVE-2017-0199)
RCE-CVE-2017-0199-detection-analysisMaturityPoCVerified exploit

Repository contains a malicious Microsoft Word DOCX sample (OpenXML structure) and a blue-team oriented writeup. The exploit targets CVE-2017-0199 (Office/Word remote code execution via external template/HTA retrieval). Structure/purpose: - README.md: Detailed ANY.RUN sandbox detonation report, attack chain narrative, and IOCs (domain tt.vg, URLs /BVhaS, resolved IPs). Describes Word making GET/HEAD requests and dropping temp/cache artifacts; includes example hunting query. - OpenXML parts (e.g., word/document.xml, word/settings.xml, relationships): The actual weaponized document internals. Key exploit mechanism (in-document): - word/_rels/settings.xml.rels defines an External attachedTemplate relationship: Target="http://ballontechnologytoupdatethenewthingstodeliveredeverywhere@tt.vg/BVhaS" with TargetMode="External". This is the critical indicator of the CVE-2017-0199-style behavior: when the document is opened, Word attempts to fetch remote content from tt.vg. Additional embedded content: - word/document.xml references multiple embedded OLE objects with ProgID "AcroExch.Document.DC" (PDF/Acrobat OLE embeddings). These appear to be decoy/embedded objects; the primary exploit trigger is the external template relationship. Observed capability/outcome: - Network beaconing to tt.vg over HTTP/HTTPS attempting to retrieve /BVhaS. The README indicates the server returned HTTP 404 in the detonation, so no second-stage payload was obtained in that run; nonetheless, the document is constructed to pull attacker-controlled remote content, which is the core exploitation capability.

BlueShield-CyberDefenseDisclosed Nov 23, 2025xmlmarkdownnetwork (phishing document -> Office RCE via external template/HTA retrieval)
Phishing-AnalysisMaturityPoCVerified exploit

This repository contains a real-world malicious DOCX file ('BankPaymAdviceVend.Report.docx') that exploits CVE-2017-0199, a remote code execution vulnerability in Microsoft Word (versions 2007–2016). The exploit is triggered when a user opens the document, causing Word to fetch and attempt to execute a remote HTA payload from the attacker-controlled domain 'tt.vg' (e.g., http://tt.vg/BVhaS). The repository provides a comprehensive blue-team analysis, including network indicators (domain, URLs, IPs), dropped files (such as EMF images in the browser cache and .tmp files), and registry keys accessed during exploitation. The structure consists of the malicious DOCX and its internal Office XML components, with the main exploit vector being an external template reference in 'word/_rels/settings.xml.rels' pointing to the attacker's server. The README.md offers detailed behavioral analysis, IOCs, and detection guidance, making this repository valuable for defenders seeking to understand and detect this exploit in enterprise environments.

BlueShield-CyberDefenseDisclosed Nov 23, 2025documentnetwork
htattackMaturityPoCVerified exploit

This repository contains a Python 2 script (htattack.py) that implements an exploit for CVE-2017-0199, a remote code execution vulnerability in Microsoft Office's handling of RTF documents. The script acts as a malicious HTTP server that serves a payload (such as a Meterpreter shell) to victims who open a specially crafted RTF file. When the victim's Office application requests the payload, the server responds with either the executable or an HTML Application (HTA) script that uses PowerShell to download and execute the payload on the victim's Windows system. The repository includes a README with usage instructions and a reference to a demonstration video. The main exploit logic is contained in htattack.py, which handles incoming HTTP requests and serves the appropriate malicious content. The exploit requires the attacker to host the payload and run the script, and the victim must open a malicious RTF document that triggers the exploit. The attack vector is network-based, leveraging HTTP to deliver the payload. Several fingerprintable endpoints are present, including the attacker's payload URL, local file paths on both the attacker's and victim's systems, and the use of PowerShell for execution.

kn0wm4dDisclosed Apr 24, 2017pythonnetwork
CVE-2017-0199MaturityPoCVerified exploit

This repository provides a Python-based exploit toolkit for CVE-2017-0199, a remote code execution vulnerability in Microsoft Office. The main script, 'cve-2017-0199_toolkit.py', allows users to generate malicious RTF or PPSX files that, when opened by a vulnerable Office installation, will fetch and execute attacker-specified payloads. The toolkit supports both local and remote payload delivery, including EXE files (such as Meterpreter shells), HTA/SCT scripts, or custom files. The script can also serve payloads over HTTP, acting as a simple web server. The README provides detailed usage scenarios and command-line options, demonstrating how to generate malicious documents and deliver payloads. The exploit is operational and can be used to achieve remote code execution on unpatched Microsoft Office installations. The repository contains three files: a detailed README, a TODO list, and the main exploit script written in Python.

bhdreshDisclosed Apr 17, 2017pythonnetwork
CVE-2017-0199MaturityPoCVerified exploit

This repository contains a Python 3 script ('cve-2017-0199_toolkit_3.py') that implements an exploit for CVE-2017-0199, a remote code execution vulnerability in Microsoft Office. The toolkit can generate malicious RTF or PPSX files that, when opened by a vulnerable Office installation, cause the application to fetch and execute a remote payload (such as a Meterpreter shell or custom executable) via a crafted HTA or SCT file. The script supports two main modes: 'gen' (generation of malicious files) and 'exp' (exploitation/delivery of payloads). It allows the attacker to specify URLs or local paths for payloads and HTA/SCT files, and can obfuscate the generated RTF files. The exploit works by running a local HTTP server to deliver the malicious content and payloads to the victim. The README provides a brief overview and notes that the script has been updated for Python 3 compatibility. The repository is operational and suitable for penetration testing or red teaming against unpatched Microsoft Office installations.

kash-123Disclosed Sep 10, 2024pythonnetwork
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationOfficeapplication
Microsoft CorporationWindows 7operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Vistaoperating_system
Phillips 66Intellispace Portalapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence31

Every observed campaign linking this CVE to a named adversary.

Associated malware24

Malware families riding this exploit, with evidence and IOCs.

Detection signatures2

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity15

Community discussion across Reddit, Mastodon, and other social sources.