Microsoft Word 2013 Service Pack 1 vulnerabilities
22 vulnerabilities
Known vulnerabilities in Microsoft Word 2013 Service Pack 1, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.
CVE-2021-40486microsoftmicrosoft office 2019+13
EPSS score5.99%
Microsoft Word Remote Code Execution VulnerabilityCVE-2021-1716microsoft365_apps+21EPSS score3.89%
Microsoft Word Remote Code Execution VulnerabilityCVE-2021-1715microsoft365_apps+21EPSS score3.89%
Microsoft Word Remote Code Execution VulnerabilityCVE-2021-31180microsoft365_apps+7EPSS score2.34%
Microsoft Office Graphics Remote Code Execution VulnerabilityCVE-2021-28453microsoft365_apps+20EPSS score4.05%
Microsoft Word Remote Code Execution VulnerabilityCVE-2020-16933microsoft365_apps+17EPSS score2.74%
<p>A security feature bypass vulnerability exists in Microsoft Word software when it fails to properly handle .LNK files. 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.</p>
<p>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.</p>
<p>The security update addresses the vulnerability by correcting how Microsoft Word handles these files.</p>CVE-2020-1583microsoft365_apps+21EPSS score4.91%
An information disclosure vulnerability exists when Microsoft Word improperly discloses the contents of its memory. An attacker who exploited the vulnerability could use the information to compromise the user’s computer or data.
To exploit the vulnerability, an attacker could craft a special document file and then convince the user to open it. An attacker must know the memory address location where the object was created.
The update addresses the vulnerability by changing the way certain Word functions handle objects in memory.CVE-2020-1503microsoft365_apps+21EPSS score4.55%
An information disclosure vulnerability exists when Microsoft Word improperly discloses the contents of its memory. An attacker who exploited the vulnerability could use the information to compromise the user’s computer or data.
To exploit the vulnerability, an attacker could craft a special document file and then convince the user to open it. An attacker must know the memory address location where the object was created.
The update addresses the vulnerability by changing the way certain Word functions handle objects in memory.CVE-2020-1218microsoft365_apps+21EPSS score3.83%
<p>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.</p>
<p>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.</p>
<p>The security update addresses the vulnerability by correcting how Microsoft Word handles files in memory.</p>CVE-2020-17020microsoft365_apps+8EPSS score1.26%
Microsoft Word Security Feature Bypass VulnerabilityCVE-2022-41061microsoft365_apps+19EPSS score1.21%
Microsoft Word Remote Code Execution VulnerabilityCVE-2022-41103microsoft365_apps+19EPSS score0.92%
Microsoft Word Information Disclosure VulnerabilityCVE-2022-41060microsoft365_apps+18EPSS score0.79%
Microsoft Word Information Disclosure VulnerabilityCVE-2022-29107microsoft365_apps+11EPSS score3.06%
Microsoft Office Security Feature Bypass VulnerabilityCVE-2022-24511microsoft365_apps+10EPSS score1.09%
Microsoft Office Word Tampering VulnerabilityCVE-2019-1201microsoftmicrosoft office 2010 service pack 2+21EPSS score4.86%
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: 1CVE-2019-1034microsoftmicrosoft office 2010 service pack 2+19EPSS score4.88%
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.CVE-2023-21716microsoftmicrosoft 365 apps for enterprise+22EPSS score84.80%
Microsoft Word Remote Code Execution VulnerabilityCVE-2023-36761microsoft365_apps+8KEVEPSS score19.57%
Microsoft Word Information Disclosure VulnerabilityCVE-2023-36895microsoft365_apps+9EPSS score1.05%
Microsoft Outlook Remote Code Execution Vulnerability