Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2017-8570: Microsoft Office Object-Handling Remote Code Execution

Published Jul 11, 2017 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS89.9%100th percentile
CISA KEVYesAdded Feb 25, 2022
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2017-8570CWE-119

CVE-2017-8570 is a remote code execution vulnerability in Microsoft Office caused by improper handling of objects in memory when opening a specially crafted file. Successful exploitation executes attacker-controlled code in the security context of the current user. Observed exploit documents use OLE objects and moniker-based references to trigger scriptlet execution, including RTF documents containing embedded Package and OLE2Link objects and PowerPoint slideshows referencing external OLE objects. The vulnerability has been exploited in phishing campaigns to deliver downloaders, information stealers, and backdoors.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

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

An attacker can execute code and perform actions with the current user's permissions. Observed exploitation has launched embedded executables or retrieved additional payloads, leading to malware installation and subsequent information theft, surveillance, or remote control. Those follow-on capabilities depend on the installed payload; the vulnerability itself does not establish execution with privileges above those of the current user.

Mitigation

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

Avoid opening untrusted Office files received through email, instant messaging, or websites. Use attachment filtering and phishing-awareness training to reduce exposure to malicious documents. Attack Surface Reduction rules that prevent Office applications from creating child processes can disrupt associated payload-delivery chains but do not replace the security update.

Remediation

Patch, then assume compromise.

Apply the Microsoft security update released on July 11, 2017, which corrects how Microsoft Office handles files in memory.

Public exploits

Exploits

3 exploits validated by Mallory's analysis. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
ppsx-file-generatorThis 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.temesgeny · Disclosed Jul 24, 2017 · python · fileOperationalCVE-2017-8570This 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.Drac0nids · Disclosed Jan 3, 2019 · bash · phishing/documentOperationalCVE-2017-8570This 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).rxwx · Disclosed Jan 9, 2018 · python · jscript · filePoC
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 CorporationMicrosoft Officeapplication
FAQ

Frequently asked questions

Is CVE-2017-8570 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Feb 25, 2022.
Is there a public exploit for CVE-2017-8570?
Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2017-8570, the earliest disclosed Jul 24, 2017.
Is there a patch for CVE-2017-8570?
Apply the Microsoft security update released on July 11, 2017, which corrects how Microsoft Office handles files in memory.
What products are affected by CVE-2017-8570?
Microsoft Corporation Microsoft Office.
How severe is CVE-2017-8570?
CVE-2017-8570 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 89.9% (100th percentile) as of Oct 16, 2026.
Mallory platform

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, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence10Every report linking this CVE to a named adversary.
Associated malware25Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.