CVE-2019-1201 Vulnerability Analysis & Exploit Details

CVE-2019-1201
Vulnerability Scoring

7.8
/10
Very High Risk

Highly exploitable, CVE-2019-1201 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: Required
    User interaction is necessary for successful exploitation.

CVE-2019-1201 Details

Status: Modified

Last updated: 🕟 21 Nov 2024, 04:36 UTC
Originally published on: 🕘 14 Aug 2019, 21:15 UTC

Time between publication and last update: 1925 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CVE-2019-1201 Vulnerability Summary

CVE-2019-1201: 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

Assessing the Risk of CVE-2019-1201

Access Complexity Graph

The exploitability of CVE-2019-1201 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2019-1201

With low attack complexity and no required privileges, CVE-2019-1201 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2019-1201, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2019-1201, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2019-1201 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2019-1201 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2019-1201 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 2.299% (probability of exploit)

EPSS Percentile: 89.68% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 10.319999999999993% of others.

CVE-2019-1201 References

External References

CWE Common Weakness Enumeration

NVD-CWE-noinfo

Vulnerable Configurations

  • cpe:2.3:a:microsoft:office:2010:sp2:*:*:*:*:*:*
    cpe:2.3:a:microsoft:office:2010:sp2:*:*:*:*:*:*
  • cpe:2.3:a:microsoft:office:2016:*:*:*:*:mac_os:*:*
    cpe:2.3:a:microsoft:office:2016:*:*:*:*:mac_os:*:*
  • cpe:2.3:a:microsoft:office:2019:*:*:*:*:*:*:*
    cpe:2.3:a:microsoft:office:2019:*:*:*:*:*:*:*
  • cpe:2.3:a:microsoft:office:2019:*:*:*:*:macos:*:*
    cpe:2.3:a:microsoft:office:2019:*:*:*:*:macos:*:*
  • cpe:2.3:a:microsoft:office_365_proplus:-:*:*:*:*:*:*:*
    cpe:2.3:a:microsoft:office_365_proplus:-:*:*:*:*:*:*:*
  • cpe:2.3:a:microsoft:office_online_server:-:*:*:*:*:*:*:*
    cpe:2.3:a:microsoft:office_online_server:-:*:*:*:*:*:*:*
  • cpe:2.3:a:microsoft:office_web_apps:2010:sp2:*:*:*:*:*:*
    cpe:2.3:a:microsoft:office_web_apps:2010:sp2:*:*:*:*:*:*
  • cpe:2.3:a:microsoft:office_web_apps_server:2013:sp1:*:*:*:*:*:*
    cpe:2.3:a:microsoft:office_web_apps_server:2013:sp1:*:*:*:*:*:*
  • cpe:2.3:a:microsoft:sharepoint_enterprise_server:2013:sp1:*:*:*:*:*:*
    cpe:2.3:a:microsoft:sharepoint_enterprise_server:2013:sp1:*:*:*:*:*:*
  • cpe:2.3:a:microsoft:sharepoint_enterprise_server:2016:*:*:*:*:*:*:*
    cpe:2.3:a:microsoft:sharepoint_enterprise_server:2016:*:*:*:*:*:*:*
  • cpe:2.3:a:microsoft:sharepoint_server:2010:sp2:*:*:*:*:*:*
    cpe:2.3:a:microsoft:sharepoint_server:2010:sp2:*:*:*:*:*:*
  • cpe:2.3:a:microsoft:sharepoint_server:2019:*:*:*:*:*:*:*
    cpe:2.3:a:microsoft:sharepoint_server:2019:*:*:*:*:*:*:*
  • cpe:2.3:a:microsoft:word:2010:sp2:*:*:*:*:*:*
    cpe:2.3:a:microsoft:word:2010:sp2:*:*:*:*:*:*
  • cpe:2.3:a:microsoft:word:2013:sp1:*:*:*:*:*:*
    cpe:2.3:a:microsoft:word:2013:sp1:*:*:*:*:*:*
  • cpe:2.3:a:microsoft:word:2013:sp1:*:*:rt:*:*:*
    cpe:2.3:a:microsoft:word:2013:sp1:*:*:rt:*:*:*
  • cpe:2.3:a:microsoft:word:2016:*:*:*:*:*:*:*
    cpe:2.3:a:microsoft:word:2016:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2019-1201: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-3809 – The Debug Log Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the auto-refresh debug log in all versions up to, and i...
  • CVE-2025-2111 – The Insert Headers And Footers plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.1.1. This i...
  • CVE-2024-13926 – The WP-Syntax WordPress plugin through 1.2 does not properly handle input, allowing an attacker to create a post containing a large number of tags,...
  • CVE-2025-3103 – The CLEVER - HTML5 Radio Player With History - Shoutcast and Icecast - Elementor Widget Addon plugin for WordPress is vulnerable to arbitrary file ...
  • CVE-2025-3275 – The Themesflat Addons For Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the TF E Slider widget in all versions up...