External risk intelligence

Microsoft Office Memory Handling Vulnerability Allows Code Execution.

CVE advisoryKnown Exploit

CVE-2017-8570

A vulnerability in Microsoft Office allows remote code execution by exploiting how memory objects are handled. This could impact organizations by enabling attackers to gain system control and access sensitive data, posing a significant business risk.

1Halo Surface Signal

Remote Code Execution

Microsoft Office

2007201020132016

External exposure likelihood

Halo Surface Signal score for CVE-2017-8570

This vulnerability affects Microsoft Office, a desktop productivity suite. It requires a user to open a specially crafted file, meaning it is a client-side application typically used on isolated or internal workstations rather than an internet-facing service, gateway, or network appliance.

Horizon Alert

Summary of the vulnerability and why it matters

Microsoft Office contains a vulnerability where the handling of memory objects can be exploited. This flaw may allow an attacker to execute arbitrary code. The potential impact includes unauthorized system control and data compromise.

  • Vulnerable Microsoft Office software
  • Improper handling of memory objects
  • Code execution and data compromise

Attack Path

How an attacker could exploit the issue

Microsoft Office contains a remote code execution vulnerability that occurs due to how it handles objects in memory. This vulnerability can be exploited to allow an attacker to execute arbitrary code within the context of the logged-in user. Such an attack could lead to a complete compromise of the affected system.

  • Exposure condition: Local system access.
  • Attacker starting point: User opens malicious file.
  • Trigger and result: Memory object handling flaw leads to code execution.

Live Threat

Current exploitation, exposure, and threat context

A vulnerability in Microsoft Office could allow attackers to execute malicious code. This could occur if an organization's employees open specially crafted documents. Such an attack could lead to significant business risk by compromising systems and data.

  • Likely attacker skill level: Not specified.
  • Required access or conditions: User opens malicious file.
  • Business risk or urgency: High.

Priority actions

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in Microsoft Office allows for remote code execution when handling objects in memory. Organizations should prioritize identifying all systems running affected versions of Microsoft Office, as attackers could potentially gain control of these systems. Addressing this vulnerability requires a structured approach to minimize business risk and protect sensitive data.

  • Find affected Microsoft Office assets.
  • Reduce exposure or isolate risk.
  • Apply vendor fix and validate.
  • Monitor for related issues.

Frequently asked questions

What is Microsoft Office, and how is it used?

Microsoft Office is a suite of productivity software applications. People commonly use it for tasks like word processing, creating spreadsheets, and preparing presentations on their computers.

What is the weakness in Microsoft Office described by CVE-2017-8570?

CVE-2017-8570 is a remote code execution vulnerability. It happens because Microsoft Office doesn't handle certain objects in its memory correctly, potentially allowing malicious code to run.

How can this Microsoft Office vulnerability be triggered?

An attacker would typically need a user to open a specially crafted file. The vulnerability is not triggered if the user does not interact with such a file.

Who should be concerned about this Microsoft Office vulnerability?

Organizations whose employees use Microsoft Office on internal workstations should be concerned. The Halo Surface Signal indicates this is an internal threat, meaning it affects software used within a company's network rather than internet-facing services.

What is the first step to address this threat in Microsoft Office?

The initial step is to identify all systems within your organization that are running the affected versions of Microsoft Office.

References