CVE-2019-1200

Microsoft Outlook Remote Code Execution Vulnerability

N/A
Published: August 14, 2019 at 08:55 PM UTC
Updated: June 17, 2026 at 02:28 AM UTC
4 products affected across 1 vendorOfficeOutlookOffice 365 ProPlus

Using Microsoft Office 2019 by Microsoft?

Get instant alerts when new vulnerabilities affect Microsoft Office 2019 - 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 Outlook 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 Outlook 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. Note that the Preview Pane is not an attack vector for this vulnerability. The security update addresses the vulnerability by correcting how Microsoft Outlook handles files in memory.

Affected

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

16.0.0 ≤ v < publication16.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
13.0.0.0 ≤ v < publication15.0.0.0 ≤ v < publication16.0.0.0 ≤ v < publication13.0.0.015.0.0.016.0.0.020102010 sp220132013 sp12016
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
19.0.0 ≤ v < https://aka.ms/OfficeSecurityReleases19.0.0
Affected range stops below https://aka.ms/OfficeSecurityReleases, 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