msrc.microsoft.com Open in urlscan Pro
2620:1ec:bdf::45  Public Scan

Form analysis
0 forms found in the DOM

Text Content

You need to enable JavaScript to run this app.
Skip to contentMicrosoft
MSRC
Security Updates
Acknowledgements
Developer

Feedback and support

Sign in to your account
Sign in


We use optional cookies to improve your experience on our websites, such as
through social media connections, and to display personalized advertising based
on your online activity. If you reject optional cookies, only cookies necessary
to provide you the services will be used. You may change your selection by
clicking “Manage Cookies” at the bottom of the page. Privacy Statement
Third-Party Cookies

Accept Reject Manage cookies

Looking for email notifications? Please create your profile with your preferred
email address to sign up for notifications. See our blog post for more
information .

Go to profile to subscribeHide for nowDon't show again
 1. MSRC
    MSRC
    
 2. Customer Guidance
    Customer Guidance
    
 3. Security Update Guide
    Security Update Guide
    
 4. Vulnerabilities
    Vulnerabilities
    
 5. CVE 2023 36884
    CVE 2023 36884


OFFICE AND WINDOWS HTML REMOTE CODE EXECUTION VULNERABILITY

On this page
CVE-2023-36884Security Vulnerability

Released: Jul 11, 2023 Last updated: Jul 12, 2023

Assigning CNA:

This CVE was issued by Microsoft
Microsoft

CVE-2023-36884 

Impact: Remote Code Execution

Max Severity: Important

CVSS:3.1 8.3 / 8.1

Base score metrics: 8.3 / Temporal score metrics: 8.1
Expand all
Collapse all
Metric

Value



Base score metrics(8)
Attack Vector
This metric reflects the context by which vulnerability exploitation is
possible. The Base Score increases the more remote (logically, and physically)
an attacker can be in order to exploit the vulnerable component.
Network
The vulnerable component is bound to the network stack and the set of possible
attackers extends beyond the other options listed, up to and including the
entire Internet. Such a vulnerability is often termed 'remotely exploitable' and
can be thought of as an attack being exploitable at the protocol level one or
more network hops away (e.g., across one or more routers).
Attack Complexity
This metric describes the conditions beyond the attacker’s control that must
exist in order to exploit the vulnerability. Such conditions may require the
collection of more information about the target or computational exceptions. The
assessment of this metric excludes any requirements for user interaction in
order to exploit the vulnerability. If a specific configuration is required for
an attack to succeed, the Base metrics should be scored assuming the vulnerable
component is in that configuration.
High
A successful attack depends on conditions beyond the attacker's control. That
is, a successful attack cannot be accomplished at will, but requires the
attacker to invest in some measurable amount of effort in preparation or
execution against the vulnerable component before a successful attack can be
expected. For example, a successful attack may require an attacker to: gather
knowledge about the environment in which the vulnerable target/component exists;
prepare the target environment to improve exploit reliability; or inject
themselves into the logical network path between the target and the resource
requested by the victim in order to read and/or modify network communications
(e.g., a man in the middle attack).
Privileges Required
This metric describes the level of privileges an attacker must possess before
successfully exploiting the vulnerability.
None
The attacker is unauthorized prior to attack, and therefore does not require any
access to settings or files to carry out an attack.
User Interaction
This metric captures the requirement for a user, other than the attacker, to
participate in the successful compromise the vulnerable component. This metric
determines whether the vulnerability can be exploited solely at the will of the
attacker, or whether a separate user (or user-initiated process) must
participate in some manner.
Required
Successful exploitation of this vulnerability requires a user to take some
action before the vulnerability can be exploited.
Scope
Does a successful attack impact a component other than the vulnerable component?
If so, the Base Score increases and the Confidentiality, Integrity and
Authentication metrics should be scored relative to the impacted component.
Changed
An exploited vulnerability can affect resources beyond the security scope
managed by the security authority of the vulnerable component. In this case, the
vulnerable component and the impacted component are different and managed by
different security authorities.
Confidentiality
This metric measures the impact to the confidentiality of the information
resources managed by a software component due to a successfully exploited
vulnerability. Confidentiality refers to limiting information access and
disclosure to only authorized users, as well as preventing access by, or
disclosure to, unauthorized ones.
High
There is total loss of confidentiality, resulting in all resources within the
impacted component being divulged to the attacker. Alternatively, access to only
some restricted information is obtained, but the disclosed information presents
a direct, serious impact.
Integrity
This metric measures the impact to integrity of a successfully exploited
vulnerability. Integrity refers to the trustworthiness and veracity of
information.
High
There is a total loss of integrity, or a complete loss of protection. For
example, the attacker is able to modify any/all files protected by the impacted
component. Alternatively, only some files can be modified, but malicious
modification would present a direct, serious consequence to the impacted
component.
Availability
This metric measures the impact to the availability of the impacted component
resulting from a successfully exploited vulnerability. It refers to the loss of
availability of the impacted component itself, such as a networked service
(e.g., web, database, email). Since availability refers to the accessibility of
information resources, attacks that consume network bandwidth, processor cycles,
or disk space all impact the availability of an impacted component.
High
There is total loss of availability, resulting in the attacker being able to
fully deny access to resources in the impacted component; this loss is either
sustained (while the attacker continues to deliver the attack) or persistent
(the condition persists even after the attack has completed). Alternatively, the
attacker has the ability to deny some availability, but the loss of availability
presents a direct, serious consequence to the impacted component (e.g., the
attacker cannot disrupt existing connections, but can prevent new connections;
the attacker can repeatedly exploit a vulnerability that, in each instance of a
successful attack, leaks a only small amount of memory, but after repeated
exploitation causes a service to become completely unavailable).


Temporal score metrics(3)
Exploit Code Maturity
This metric measures the likelihood of the vulnerability being attacked, and is
typically based on the current state of exploit techniques, exploit code
availability, or active, 'in-the-wild' exploitation.
Functional
Functional exploit code is available. The code works in most situations where
the vulnerability exists.
Remediation Level
The Remediation Level of a vulnerability is an important factor for
prioritization. The typical vulnerability is unpatched when initially published.
Workarounds or hotfixes may offer interim remediation until an official patch or
upgrade is issued. Each of these respective stages adjusts the temporal score
downwards, reflecting the decreasing urgency as remediation becomes final.
Unavailable
There is either no solution available or it is impossible to apply.
Report Confidence
This metric measures the degree of confidence in the existence of the
vulnerability and the credibility of the known technical details. Sometimes only
the existence of vulnerabilities are publicized, but without specific details.
For example, an impact may be recognized as undesirable, but the root cause may
not be known. The vulnerability may later be corroborated by research which
suggests where the vulnerability may lie, though the research may not be
certain. Finally, a vulnerability may be confirmed through acknowledgement by
the author or vendor of the affected technology. The urgency of a vulnerability
is higher when a vulnerability is known to exist with certainty. This metric
also suggests the level of technical knowledge available to would-be attackers.
Confirmed
Detailed reports exist, or functional reproduction is possible (functional
exploits may provide this). Source code is available to independently verify the
assertions of the research, or the author or vendor of the affected code has
confirmed the presence of the vulnerability.

Please see Common Vulnerability Scoring System for more information on the
definition of these metrics.


EXECUTIVE SUMMARY

Microsoft is investigating reports of a series of remote code execution
vulnerabilities impacting Windows and Office products. Microsoft is aware of
targeted attacks that attempt to exploit these vulnerabilities by using
specially-crafted Microsoft Office documents.

An attacker could create a specially crafted Microsoft Office document that
enables them to perform remote code execution in the context of the victim.
However, an attacker would have to convince the victim to open the malicious
file.

Upon completion of this investigation, Microsoft will take the appropriate
action to help protect our customers. This might include providing a security
update through our monthly release process or providing an out-of-cycle security
update, depending on customer needs.

Please see the Microsoft Threat Intelligence Blog Entry for important
information about steps you can take to protect your system from this
vulnerability.

This CVE will be updated with new information and links to security updates when
they become available. If you wish to be notified when these updates are
released, we recommend that you register for the security notifications mailer
to be alerted of content changes to this CVE. See Microsoft Technical Security
Notifications and Security Update Guide Notification System News: Create your
profile now – Microsoft Security Response Center.


EXPLOITABILITY

The following table provides an exploitability assessment for this vulnerability
at the time of original publication.
Publicly Disclosed

Exploited

Latest Software Release

Yes
Yes
Exploitation Detected


MITIGATIONS

 * Customers who use Microsoft Defender for Office are protected from
   attachments that attempt to exploit this vulnerability.
 * In current attack chains, the use of the Block all Office applications from
   creating child processes Attack Surface Reduction Rule will prevent the
   vulnerability from being exploited.
 * Organizations who cannot take advantage of these protections can set the
   FEATURE_BLOCK_CROSS_PROTOCOL_FILE_NAVIGATION registry key to avoid
   exploitation. No OS restart is required, but restarting the applications that
   have had the registry key added for them is recommended in case the value was
   already queried and is cached. Please note that while these registry settings
   would mitigate exploitation of this issue, it could affect regular
   functionality for certain use cases related to these applications. For this
   reason, we suggest testing. To disable the mitigation, delete the registry
   key or set it to “0”.
 * Add the following application names to this registry key as values of type
   REG_DWORD with data 1.:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Internet
Explorer\Main\FeatureControl\FEATURE_BLOCK_CROSS_PROTOCOL_FILE_NAVIGATION

 * Excel.exe
 * Graph.exe
 * MSAccess.exe
 * MSPub.exe
 * Powerpnt.exe
 * Visio.exe
 * WinProj.exe
 * WinWord.exe
 * Wordpad.exe

Please see the Microsoft Threat Intelligence Blog Entry for more detailed
information.


FAQ

If I'm running Office365 Semi-Annual Channel Extended, am I affected by this
vulnerability?

Office365 Semi-Annual Channel Extended (specifically versions 2208 and 2202) are
affected. Microsoft 365 Apps Semi-Annual Channel Extended (specifically versions
2208 and 2202) are affected. However, Microsoft 365 Semi-Annual Channel version
2302 (and all later versions) are protected from this vulnerability.. Please see
Update history for Microsoft 365 Apps (listed by date) for information about
those channels and their versions.


ACKNOWLEDGEMENTS

 * Microsoft Threat Intelligence
 * Vlad Stolyarov, Clement Lecigne and Bahare Sabouri of Google’s Threat
   Analysis Group (TAG)
 * Paul Rascagneres with Volexity
 * Tom Lancaster with Volexity
 * Microsoft Office Product Group Security Team

Microsoft recognizes the efforts of those in the security community who help us
protect customers through coordinated vulnerability disclosure. See
Acknowledgements for more information.


SECURITY UPDATES

To determine the support lifecycle for your software, see the Microsoft Support
Lifecycle.
Updates CVSS
Release date Descending
Edit columns
Download

Clear
Release Date

Product

Platform

Impact

Max Severity

Article

Download

Build Number

Details

Jul 11, 2023
Windows 10 for x64-based Systems
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows 10 for 32-bit Systems
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows 10 Version 22H2 for 32-bit Systems
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows 10 Version 22H2 for ARM64-based Systems
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows 10 Version 22H2 for x64-based Systems
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows 11 Version 22H2 for x64-based Systems
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows 11 Version 22H2 for ARM64-based Systems
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows 10 Version 21H2 for x64-based Systems
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows 10 Version 21H2 for ARM64-based Systems
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows 10 Version 21H2 for 32-bit Systems
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows 11 version 21H2 for ARM64-based Systems
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows 11 version 21H2 for x64-based Systems
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows Server 2022 (Server Core installation)
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows Server 2022
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows Server 2019 (Server Core installation)
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows Server 2019
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows 10 Version 1809 for ARM64-based Systems
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows 10 Version 1809 for x64-based Systems
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows 10 Version 1809 for 32-bit Systems
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Microsoft Word 2013 Service Pack 1 (64-bit editions)
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Microsoft Word 2013 Service Pack 1 (32-bit editions)
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Microsoft Word 2016 (64-bit edition)
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Microsoft Word 2016 (32-bit edition)
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Microsoft Office LTSC 2021 for 32-bit editions
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Microsoft Office LTSC 2021 for 64-bit editions
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Microsoft Office 2019 for 64-bit editions
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows Server 2012
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core
installation)
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows Server 2008 R2 for x64-based Systems Service Pack 1
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core
installation)
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows Server 2008 for x64-based Systems Service Pack 2
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows Server 2008 for 32-bit Systems Service Pack 2
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows Server 2016 (Server Core installation)
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows Server 2016
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows 10 Version 1607 for x64-based Systems
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows 10 Version 1607 for 32-bit Systems
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows Server 2012 R2
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows Server 2012 (Server Core installation)
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Microsoft Office 2019 for 32-bit editions
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884
Jul 11, 2023
Windows Server 2012 R2 (Server Core installation)
-
Remote Code Execution
Important
-
-
-
CVE-2023-36884

All results loaded
Loaded all 41 rows


DISCLAIMER

The information provided in the Microsoft Knowledge Base is provided "as is"
without warranty of any kind. Microsoft disclaims all warranties, either express
or implied, including the warranties of merchantability and fitness for a
particular purpose. In no event shall Microsoft Corporation or its suppliers be
liable for any damages whatsoever including direct, indirect, incidental,
consequential, loss of business profits or special damages, even if Microsoft
Corporation or its suppliers have been advised of the possibility of such
damages. Some states do not allow the exclusion or limitation of liability for
consequential or incidental damages so the foregoing limitation may not apply.


REVISIONS

version

revisionDate

description

1.1
Jul 12, 2023

Updated FAQ information. This is an informational change only.

1.0
Jul 11, 2023

Information published.


How satisfied are you with the MSRC Security Update Guide?

Not satisfied12345Very satisfied