CVE-2019-1034

Microsoft Word Remote Code Execution Vulnerability

N/A
Published: June 12, 2019 at 01:49 PM UTC
Updated: June 17, 2026 at 02:27 AM UTC
13 products affected across 1 vendorOfficeOffice 2019SharePoint Server

Using Microsoft SharePoint Enterprise Server 2016 by Microsoft?

Get instant alerts when new vulnerabilities affect Microsoft SharePoint Enterprise Server 2016 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 5%

Description

A remote code execution vulnerability exists in Microsoft Word software when it fails to properly handle objects in memory. An attacker who successfully exploited the vulnerability could use a specially crafted file to perform actions in the security context of the current user. For example, the file could then take actions on behalf of the logged-on user with the same permissions as the current user. To exploit the vulnerability, a user must open a specially crafted file with an affected version of Microsoft Word software. In an email attack scenario, an attacker could exploit the vulnerability by sending the specially crafted file to the user and convincing the user to open the file. In a web-based attack scenario, an attacker could host a website (or leverage a compromised website that accepts or hosts user-provided content) that contains a specially crafted file that is designed to exploit the vulnerability. However, an attacker would have no way to force the user to visit the website. Instead, an attacker would have to convince the user to click a link, typically by way of an enticement in an email or Instant Messenger message, and then convince the user to open the specially crafted file. The security update addresses the vulnerability by correcting how Microsoft Word handles files in memory.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

13.0.0.0 ≤ v < publication
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
16.0.0 ≤ v < publication2010 sp220162019
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
16.0.0 ≤ v < publication19.0.0 ≤ v < https://aka.ms/OfficeSecurityReleases16.0.019.0.0
Affected range stops below https://aka.ms/OfficeSecurityReleases, so it looks safe — our inference, not a vendor statement
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
16.0.0 ≤ v < publication16.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
16.0.1 ≤ v < publication16.0.1
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
13.0.0 ≤ v < publication13.0.02010 sp2
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
15.0.0 ≤ v < publication15.0.02013 sp12016
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
13.0.0.0 ≤ v < publication15.0.0 ≤ v < publication13.0.0.02010 sp22019
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
13.0.0.0 ≤ v < publication15.0.1 ≤ v < publication16.0.1 ≤ v < publication13.0.0.015.0.116.0.12010 sp22013 sp12016
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
13.0.0.0 ≤ v < publication13.0.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

CVSS

Confidentiality
COMPLETE
Integrity
COMPLETE
Availability
COMPLETE
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card