Vulnerabilities

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.<br /> To exploit the vulnerability, a user must open a specially crafted file with an affected version of Microsoft Word software.<br /> Two possible email attack scenarios exist for this vulnerability:<br /> • 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.<br /> • 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.<br /> 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.<br /> The security update addresses the vulnerability by correcting how Microsoft Word handles files in memory.<br /> 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.<br /> 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 &amp;quot;Changing Keys and Values&amp;quot; Help topic in Registry Editor (Regedit.exe) or view the &amp;quot;Add and Delete Information in the Registry&amp;quot; and &amp;quot;Edit Registry Data&amp;quot; Help topics in Regedt32.exe.<br /> Outlook 2010:<br /> HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Options<br /> DWORD: DisableReadingPane<br /> Value: 1<br /> Outlook 2013:<br /> HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\Options<br /> DWORD: DisableReadingPane<br /> Value: 1<br /> Outlook 2016, Outlook 2019, and Office 365 ProPlus:<br /> HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Options<br /> DWORD: DisableReadingPane<br /> Value: 1

An elevation of privilege vulnerability exists when reparse points are created by sandboxed processes allowing sandbox escape. An attacker who successfully exploited the vulnerability could use the sandbox escape to elevate privileges on an affected system.<br /> To exploit the vulnerability, an attacker would first have to log on to the system, and then run a specially crafted application to take control over the affected system.<br /> The security update addresses the vulnerability by preventing sandboxed processes from creating reparse points targeting inaccessible files.

An information disclosure vulnerability exists in SymCrypt during the OAEP decryption stage. An attacker who successfully exploited this vulnerability could obtain information to further compromise the user’s system.<br /> To exploit this vulnerability, an attacker would have to log on to an affected system and run a specially crafted application. The vulnerability would not allow an attacker to execute code or to elevate user rights directly, but it could be used to obtain information that could be used to try to further compromise the affected system.<br /> The update addresses the vulnerability through a software change to the OAEP decoding operations.

An information disclosure vulnerability exists in Azure Active Directory (AAD) Microsoft Account (MSA) during the login request session. An attacker who successfully exploited the vulnerability could take over a user&amp;#39;s account.<br /> To exploit the vulnerability, an attacker would have to trick a user into browsing to a specially crafted website, allowing the attacker to steal the user&amp;#39;s token.<br /> The security update addresses the vulnerability by correcting how MSA handles cookies.

An elevation of privilege vulnerability exists in the way that the PsmServiceExtHost.dll handles objects in memory. An attacker who successfully exploited the vulnerability could execute code with elevated permissions.<br /> To exploit the vulnerability, a locally authenticated attacker could run a specially crafted application.<br /> The security update addresses the vulnerability by ensuring the PsmServiceExtHost.dll properly handles objects in memory.

An elevation of privilege vulnerability exists in the way that the PsmServiceExtHost.dll handles objects in memory. An attacker who successfully exploited the vulnerability could execute code with elevated permissions.<br /> To exploit the vulnerability, a locally authenticated attacker could run a specially crafted application.<br /> The security update addresses the vulnerability by ensuring the PsmServiceExtHost.dll properly handles objects in memory.

An elevation of privilege vulnerability exists in the way that the psmsrv.dll handles objects in memory. An attacker who successfully exploited the vulnerability could execute code with elevated permissions.<br /> To exploit the vulnerability, a locally authenticated attacker could run a specially crafted application.<br /> The security update addresses the vulnerability by ensuring the psmsrv.dll properly handles objects in memory.

An elevation of privilege vulnerability exists when DirectX improperly handles objects in memory. An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.<br /> To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and take control of an affected system.<br /> The update addresses the vulnerability by correcting how DirectX handles objects in memory.

An elevation of privilege vulnerability exists in the way that the rpcss.dll handles objects in memory. An attacker who successfully exploited the vulnerability could execute code with elevated permissions.<br /> To exploit the vulnerability, a locally authenticated attacker could run a specially crafted application.<br /> The security update addresses the vulnerability by ensuring the rpcss.dll properly handles objects in memory.

An elevation of privilege vulnerability exists in the way that the ssdpsrv.dll handles objects in memory. An attacker who successfully exploited the vulnerability could execute code with elevated permissions.<br /> To exploit the vulnerability, a locally authenticated attacker could run a specially crafted application.<br /> The security update addresses the vulnerability by ensuring the ssdpsrv.dll properly handles objects in memory.

An elevation of privilege vulnerability exists in the way that the unistore.dll handles objects in memory. An attacker who successfully exploited the vulnerability could execute code with elevated permissions.<br /> To exploit the vulnerability, a locally authenticated attacker could run a specially crafted application.<br /> The security update addresses the vulnerability by ensuring the unistore.dll properly handles objects in memory.

An elevation of privilege vulnerability exists in the way that the wcmsvc.dll handles objects in memory. An attacker who successfully exploited the vulnerability could execute code with elevated permissions.<br /> To exploit the vulnerability, a locally authenticated attacker could run a specially crafted application.<br /> The security update addresses the vulnerability by ensuring the wcmsvc.dll properly handles objects in memory.