msrc.microsoft.com Open in urlscan Pro
2620:1ec:4e:1::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 2022 21980
    CVE 2022 21980


MICROSOFT EXCHANGE SERVER ELEVATION OF PRIVILEGE VULNERABILITY

On this page
CVE-2022-21980Security Vulnerability

Released: Aug 9, 2022 Last updated: Oct 11, 2022

Assigning CNA:

This CVE was issued by Microsoft
Microsoft

CVE-2022-21980 

CVSS:3.1 8.0 / 7.0

Base score metrics: 8.0 / Temporal score metrics: 7.0
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.
Low
Specialized access conditions or extenuating circumstances do not exist. An
attacker can expect repeatable success against the vulnerable component.
Privileges Required
This metric describes the level of privileges an attacker must possess before
successfully exploiting the vulnerability.
Low
The attacker is authorized with (i.e., requires) privileges that provide basic
user capabilities that could normally affect only settings and files owned by a
user. Alternatively, an attacker with Low privileges may have the ability to
cause an impact only to non-sensitive resources.
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.
Unchanged
An exploited vulnerability can only affect resources managed by the same
security authority. In this case, the vulnerable component and the impacted
component are either the same, or both are managed by the same security
authority.
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.
Unproven
No exploit code is available, or an exploit is theoretical.
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.
Official Fix
A complete vendor solution is available. Either the vendor has issued an
official patch, or an upgrade is available.
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.


EXPLOITABILITY

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

Exploited

Latest Software Release

No
No
Exploitation More Likely


FAQ

Are there any more actions I need to take to be protected from this
vulnerability?

Yes. Customers running an affected version of Microsoft Exchange need to enable
Extended Protection to be protected from this vulnerability. For more
information, see Exchange Server Support for Windows Extended Protection.

Is there more information available about this release of Exchange Server?

For more information on this issue, please see The Exchange Blog.

According to the CVSS metric, privileges required is low (PR:L). Does the
attacker need to be in an authenticated role on the Exchange Server?

Yes, the attacker must be authenticated.

According to the CVSS metric, user interaction is required (UI:R). What
interaction would the user have to do?

This vulnerability requires that a user with an affected version of Exchange
Server access a malicious server. An attacker would have to host a specially
crafted server share or website. An attacker would have no way to force users to
visit this specially crafted server share or website, but would have to convince
them to visit the server share or website, typically by way of an enticement in
an email or chat message.


ACKNOWLEDGEMENTS

 * Tianze Ding (@D1iv3) with Tencent Xuanwu Lab
 * Zhiniang Peng with Sangfor
 * Yuhao Weng with Sangfor

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
Edit columns
Download

Clear
Release Date

Product

Platform

Impact

Max Severity

Article

Download

Build Number

Details

Aug 9, 2022
Microsoft Exchange Server 2016 Cumulative Update 23
-
Elevation of Privilege
Critical
 * 5019077 

 * Security Update 

 * 15.01.2507.013

CVE-2022-21980
Aug 9, 2022
Microsoft Exchange Server 2019 Cumulative Update 12
-
Elevation of Privilege
Critical
 * 5019077 

 * Security Update 

 * 15.02.1118.015

CVE-2022-21980
Aug 9, 2022
Microsoft Exchange Server 2016 Cumulative Update 22
-
Elevation of Privilege
Critical
 * 5019077 

 * Security Update 

 * 15.01.2375.032

CVE-2022-21980
Aug 9, 2022
Microsoft Exchange Server 2019 Cumulative Update 11
-
Elevation of Privilege
Critical
 * 5019077 

 * Security Update 

 * 15.02.0986.030

CVE-2022-21980
Aug 9, 2022
Microsoft Exchange Server 2013 Cumulative Update 23
-
Elevation of Privilege
Critical
 * 5019076 

 * Security Update 

 * 15.00.1497.042

CVE-2022-21980

5/5
Load more (5/5)


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

2.0
Oct 11, 2022

To address known issue of Outlook Probes not functioning properly with extended
protection turned on, Microsoft has updated the Microsoft Exchange security
updates. Please see the Exchange Team Blog for more information.

1.1
Sep 20, 2022

Added FAQ information. This is an informational change only.

1.0
Aug 9, 2022

Information published.

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