Skip to main content

Microsoft Office CVE-2017-8570

HIGH
2017-07-11 secure@microsoft.com
7.8
CVSS 3.1
Share

CVSS VectorNVD

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

7
Analysis Updated
Apr 22, 2026 - 14:01 vuln.today
v2 (cvss_changed)
Re-analysis Queued
Apr 21, 2026 - 15:22 vuln.today
cvss_changed
Analysis Generated
Mar 26, 2026 - 11:18 vuln.today
Added to CISA KEV
Oct 22, 2025 - 00:16 cisa
CISA KEV
PoC Detected
Oct 22, 2025 - 00:16 vuln.today
Public exploit code
Patch released
Oct 22, 2025 - 00:16 nvd
Patch available
CVE Published
Jul 11, 2017 - 21:29 nvd
HIGH 7.8

DescriptionNVD

Microsoft Office allows a remote code execution vulnerability due to the way that it handles objects in memory, aka "Microsoft Office Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-0243.

AnalysisAI

Remote code execution in Microsoft Office 2007-2016 allows attackers to execute arbitrary code with user privileges by delivering malicious documents containing specially crafted embedded objects. Confirmed actively exploited (CISA KEV) with multiple public exploit tools available. EPSS score of 94.25% (100th percentile) indicates near-certain exploitation attempts against vulnerable systems. Attack requires local file access and user interaction (opening the malicious document), but once triggered achieves full code execution with high impact to confidentiality, integrity, and availability. Microsoft released patches in July 2017; unpatched systems remain high-priority targets for document-based attacks.

Technical ContextAI

This vulnerability exploits Microsoft Office's Composite Moniker object handling mechanism, specifically the way Office processes embedded objects through the COM (Component Object Model) subsystem. Attackers craft malicious Office documents (particularly PowerPoint .ppsx files) containing specially structured OLE (Object Linking and Embedding) objects that trigger unsafe deserialization or object instantiation. The Composite Moniker allows chaining multiple monikers together, enabling attackers to reference remote script resources (typically hosted via HTTP) that execute when the document is opened. CPE data confirms affected versions span Office 2007 SP3, 2010 SP2, 2013 SP1 (including RT), and 2016 (both x86 and x64 architectures). While no CWE is formally assigned, the vulnerability pattern aligns with unsafe object handling and deserialization issues common in complex document processing engines. The attack surface exists because Office must support legitimate OLE embedding features for backward compatibility, creating opportunities for abuse when object references are not properly validated.

RemediationAI

Apply Microsoft's July 2017 Security Update for Office, which addresses CVE-2017-8570 across all affected versions (2007 SP3, 2010 SP2, 2013 SP1, 2016). Patches available through Windows Update, Microsoft Update Catalog, or the vendor advisory at https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/CVE-2017-8570. For systems that cannot immediately patch, implement Protected View for all Office document sources (configured via Group Policy or Trust Center settings) to force documents into sandboxed read-only mode, though this reduces productivity and may be bypassed by users. Disable OLE package activation through registry modifications (HKEY_CURRENT_USER\Software\Microsoft\Office\[version]\[application]\Security\PackagerPrompt set to 2), which prevents automatic execution of embedded objects but may break legitimate documents containing embedded content. Email gateway filtering should block or quarantine Office documents with embedded Composite Moniker objects or remote OLE references. User awareness training should emphasize risks of opening Office documents from untrusted sources, though social engineering success rates make this a weak compensating control. Given the vulnerability's age and confirmed exploitation, patching remains the only reliable long-term mitigation.

Share

CVE-2017-8570 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy