dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 25 Aug 2022.
OfficeApplication · Microsoft

CVE-2017-8570

HIGH · 7.8 CVSS v3.1 Published 2017-07-11
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
97/100
Remediation priority · Urgent
In the wild High EPSS Public exploit No privileges Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Microsoft Office contains a remote code execution vulnerability caused by improper memory handling when processing objects. The flaw allows an attacker to execute arbitrary code via specially crafted Office documents, likely through memory corruption during object parsing.

MitigationApply Microsoft security updates for Microsoft Office to address the memory handling vulnerability; avoid opening untrusted Office documents from unknown sources as an additional safeguard.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OfficeApplication
Affected:= 2007= 2010= 2013= 2016

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Microsoft Office version
    Open any Office application (Word, Excel, PowerPoint), go to File > Account > About [App] to see the exact version number (e.g., 16.0.xxxx.xxxx for Office 2016)
    Affected if The installed version is 2007, 2010, 2013, or 2016 without security updates applied
  2. Check Windows Update for Office security patches
    Open Windows Update (Windows Key + R, type: ms-settings:windowsupdate), view update history to see if KB4011262 (July 2017) or subsequent Office security updates are installed
    Affected if KB4011262 or later Office security updates are not installed on the affected Office versions
  3. Verify if file execution policy allows opening Office attachments
    Check if Protected View or macro settings are disabled: in any Office app, go to File > Options > Trust Center > Trust Center Settings > Protected View; also check File > Options > Trust Center > Trust Center Settings > Macro Settings
    Affected if Protected View is disabled and user routinely opens Office files from external sources without verification
  4. Confirm presence of vulnerable Office components
    Check if the affected Office application (particularly PowerPoint) is installed and used: open PowerPoint, verify version via File > Account > About PowerPoint
    Affected if PowerPoint 2007, 2010, 2013, or 2016 is installed and used without the security update applied

User is affected if running Microsoft Office 2007, 2010, 2013, or 2016 without the July 2017 security update (KB4011262 or later) and routinely opens Office files without Protected View enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch portal.msrc.microsoft.com →
Interim mitigation

Apply Microsoft security updates for Microsoft Office to address the memory handling vulnerability; avoid opening untrusted Office documents from unknown sources as an additional safeguard.

Recommended fix Moderate confidence

Apply Microsoft security updates for CVE-2017-8570 (MS17-013 and subsequent relevant patches); for end-of-life versions (2007, 2010), upgrade to supported Office versions (2019/2021 or Microsoft 365)

  1. Open Microsoft Update or check Windows Update for available updates
  2. Locate and install the Microsoft security update for CVE-2017-8570 (part of MS17-013 or subsequent security bulletins)
  3. Alternatively, download the specific security update from the Microsoft Update Catalog for your Office version: KB 3191858 for Office 2016, KB 3191855 for Office 2013, KB 3191852 for Office 2010, KB 3191851 for Office 2007
  4. Restart the computer after installing the update
  5. Verify the update is installed by checking installed updates via Control Panel > Programs and Features > View installed updates
  6. Ensure Microsoft Office is updated to a supported, patched version
Caveat Minimal risk from applying Microsoft security patches; however, Office 2007/2010 are end-of-life and no longer receive security updates, requiring upgrade to a supported version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Office Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-8570 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-8570 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data