Patchfirst
CVE-2017-8570 KEVPublic exploit High · 7.8 EPSS 89.9%

Microsoft Office Remote Code Execution Vulnerability

Microsoft · Office

Official description · NVD

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.

Breakdown
78.4 / 100
Exploited
Yes, in CISA KEV
Reports
5
Tactics
1/15

How an attack unfolds

Based on mappings. Select a step to see the evidence.
  1. What can follow

First seen exploited 5 months after disclosure. Public exploit code (PoC-in-GitHub) appeared 13 days after disclosure.

  1. Disclosedday 0
  2. Public exploit codePoC-in-GitHub+13 days
  3. First seen exploitedVulnCheck KEV evidence+5 mo
  4. First dated threat reportvolexity.com+11 mo
  5. Added to CISA KEVEU database agrees+5 yrs

CISA KEV listing is when exploitation was confirmed, not necessarily the first attack.

techniques

2 , grouped by in kill-chain order, 6 cited passages 2

ExecutionTA0002

Exploitation for Client Execution T1203 Medium
MITRE CTID mapping of the CVE · uncategorised
on a well-known Russian cybercrime forum, the seller offered two types of weaponized Microsoft Office documents (maldocs) to users: one that exploits a known vulnerability in Microsoft Office ([CVE-2017-8570](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2017-8570)) and another that uses a malicious
EtterSilent: the underground’s new favorite maldoc builder Intel 471, 7 Apr 2021 Original (opens in a new tab) ↗
Malicious File T1204.002 Medium
MITRE CTID mapping of the CVE · uncategorised
Lower-confidence links (1)

These come from early or generic mappings, text matching, or contradict this CVE’s details (for example a public-facing technique on a bug that needs a user to open a file). Shown for completeness.

  • Command and Scripting InterpreterT1059 machine-matched from report text

Detection

0 rules for this CVE · 74 general rules for its techniques

Rules for this CVE

0 that reference CVE-2017-8570 directly.

CVE-specific rules are not available in this build. Search SigmaHQ ↗

Sigma rules © SigmaHQ, Detection Rule License 1.1; linked, not reproduced.

What security researchers reported

Named in 5 threat reports
5 reportsIntel 471VolexityProofpoint+2Jun 2018 – Apr 2021 · 3 undated

Reports are matched by finding the exact id CVE-2017-8570 in their text; nobody has reviewed the match. One passage is shown per report, at most 320 characters, linked to the original.

Show all 5 reportsShow fewer

Also mentioned in 50 community threat pulses (AlienVault OTX)

Weaker evidence

Pulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.

References

6 links, grouped by NVD tag (5 duplicates merged)
↑ ↓ chooseEnter openEsc close