Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
HighCISA KEVExploited in the wildPublic exploit

Microsoft Office Remote Code Execution Vulnerability

IdentifiersCVE-2017-8570CWE-119

CVE-2017-8570 is a Microsoft Office remote code execution vulnerability caused by the way Microsoft Office handles objects in memory. The provided content identifies it as a memory-handling flaw in Office and notes that it has been weaponized in malicious Office documents and exploit-builder kits such as VenomKit and ThreadKit. The vulnerability has been used as an execution vector during document delivery by malware operators including Agent Tesla campaigns. Successful exploitation occurs when a victim opens a crafted Office document, leading to code execution in the context of the current user.

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 code execution on the victim system in the security context of the user who opened the malicious Office document. In observed campaigns, this execution capability was used to launch malware delivery chains, including loaders, scriptlets, batch files, and commodity malware such as Agent Tesla and other crimeware payloads. Impact therefore includes initial compromise, malware installation, follow-on payload delivery, and potential access to victim data and systems consistent with the privileges of the affected user.

Mitigation

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

Until patching is complete, reduce exposure by blocking or sandboxing untrusted Office attachments, restricting delivery of Office documents from external sources where feasible, and disabling or limiting execution paths commonly abused by malicious document chains. Use Protected View, attack surface reduction controls, email detonation/sandboxing, and endpoint protections to detect exploit-based Office document activity. User awareness measures to avoid opening unsolicited attachments also reduce risk, although user interaction remains a primary exposure point.

Remediation

Patch, then assume compromise.

Apply the Microsoft security updates that address CVE-2017-8570 for affected Microsoft Office versions. Ensure Office installations are fully patched using Microsoft-supported updates and that unsupported Office versions are upgraded to supported releases. Because the content specifically identifies this flaw as actively exploited in malicious document campaigns and exploit kits, remediation should be prioritized on endpoints that handle email attachments or untrusted Office documents.
PUBLIC EXPLOITS

Exploits

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

VALID 3 / 4 TOTALView more in app
CVE-2017-8570MaturityPoCVerified exploit

This repository contains a Bash script ('auto') and a README.md file. The script automates the process of generating a malicious Microsoft Office PPSX file exploiting CVE-2017-8570. The attacker sets their own IP address and port, and the script uses msfvenom to generate a Meterpreter reverse shell payload. It clones a toolkit from GitHub, prepares the payload, and sets up a Metasploit handler. The attacker is instructed to send the generated Invoice.ppsx file to the victim. When the victim opens the file, it triggers a download of the Meterpreter payload via PowerShell, resulting in a reverse shell connection to the attacker's machine. The main attack vector is phishing via a malicious Office document. The script is operational and automates the exploit setup, but relies on external tools and manual delivery of the malicious file.

Drac0nidsDisclosed Jan 3, 2019bashphishing/document
ppsx-file-generatorMaturityPoCVerified exploit

This repository provides a Python tool ('generate_ppsx.py') that generates a malicious PowerPoint Show (.ppsx) file and an associated XML file to exploit CVE-2017-8570, a vulnerability in Microsoft Office. The exploit works by embedding a reference to a remote XML file in the .ppsx file. The XML file, when accessed by PowerPoint, triggers PowerShell to download and execute a remote payload (such as an executable or script) from an attacker-controlled server. The README.md provides detailed usage instructions, including example command lines and required setup steps. The exploit requires the attacker to host both the payload and the XML file on a web server, and for the victim to open the crafted .ppsx file in PowerPoint. The repository contains two files: a README.md with instructions and a Python script that automates the creation of the exploit files. The main attack vector is via a malicious file, and the exploit leverages remote URLs for payload delivery and execution.

temesgenyDisclosed Jul 24, 2017pythonfile
CVE-2017-8570MaturityPoCVerified exploit

This repository is a Proof of Concept exploit for CVE-2017-8570 (the 'Composite Moniker' vulnerability in Microsoft Office). The main exploit script, 'packager_composite_moniker.py', generates a malicious RTF file that embeds a scriptlet (.sct) file using the Packager.dll trick. When a vulnerable version of Microsoft Office opens the generated RTF, it drops the SCT file into the %TEMP% directory (or a fake path) and executes it, leading to arbitrary code execution. The provided 'calc.sct' payload demonstrates code execution by launching calc.exe. The repository also includes a YARA rule for detection and an example RTF file. The exploit is a POC and does not include weaponized features such as payload customization or C2 communication. The main attack vector is via malicious file delivery (RTF document).

rxwxDisclosed Jan 9, 2018pythonjscriptfile
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

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 evidence5

Every observed campaign linking this CVE to a named adversary.

Associated malware7

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

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 activity

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