msrc.microsoft.com Open in urlscan Pro
2620:1ec:29:1::40  Public Scan

Form analysis
0 forms found in the DOM

Text Content

You need to enable JavaScript to run this app.
Skip to main contentMicrosoft
MSRC
Security Updates
Acknowledgements

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
 1. MSRC
    MSRC
    
 2. Customer Guidance
    Customer Guidance
    
 3. Security Update Guide
    Security Update Guide
    
 4. Advisories
    Advisories
    
 5. CVE 2024 38200
    CVE 2024 38200


MICROSOFT OFFICE SPOOFING VULNERABILITY NEWRECENTLY UPDATED

On this page
CVE-2024-38200
Subscribe
RSS
PowerShell
API
Security Vulnerability

Released: Aug 8, 2024

Last updated: Aug 10, 2024

Assigning CNA:
Microsoft

CVE-2024-38200 

Impact: Spoofing

Max Severity: Important

Weakness:
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
CVSS Source: Microsoft
CVSS:3.1 6.5 / 5.7
Base score metrics: 6.5 / Temporal score metrics: 5.7
Base score metrics: 6.5 / Temporal score metrics: 5.7
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.
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.
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.
None
There is no loss of integrity within 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.
None
There is no impact to availability within the impacted component.


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, public availability
of exploit code, or active, 'in-the-wild' exploitation.
Unproven
No publicly available 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 disclosedYesExploitedNoExploitability assessmentExploitation Less
Likely


MITIGATIONS

The following mitigating factors may be helpful in your situation:

Configuring the Network Security: Restrict NTLM: Outgoing NTLM traffic to remote
servers policy setting provides the ability to allow, block, or audit outgoing
NTLM traffic from a computer running Windows Server 2008, Windows Server 2008
R2, or later to any remote server running the Windows operating system.
Performing this mitigation allows you to block or audit all attempts to connect
to remote servers through NTLM authentication. Please note: Modifying this
policy setting may affect compatibility with client computers, services, and
applications.

The following mitigating factors may be helpful in your situation:

 * Add users to the Protected Users Security Group, which prevents the use of
   NTLM as an authentication mechanism. Performing this mitigation makes
   troubleshooting easier than other methods of disabling NTLM. Consider using
   it for high value accounts such as Domain Admins when possible. Please note:
   This may cause impact to applications that require NTLM, however the settings
   will revert once the user is removed from the Protected Users Group. Please
   see Protected Users Security Group for more information.
 * Block TCP 445/SMB outbound from your network by using a perimeter firewall, a
   local firewall, and via your VPN settings. This will prevent the sending of
   NTLM authentication messages to remote file shares.


FAQ

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

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.

Am I vulnerable to this issue until I install the August 13, 2024 updates?

No, we identified an alternative fix to this issue that we enabled via Feature
Flighting on 7/30/2024. Customers are already protected on all in-support
versions of Microsoft Office and Microsoft 365. Customers should still update to
the August 13, 2024 updates for the final version of the fix.

When will a final update be available to address this vulnerability?

The Security Updates table will be revised when the update is publicly
available. If you wish to be notified when these update is 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 Coming Soon: New Security Update Guide Notification System.

There are multiple update packages available for some of the affected software.
Do I need to install all the updates listed in the Security Updates table for
the software?

Yes. Customers should apply all updates offered for the software installed on
their systems. If multiple updates apply, they can be installed in any order.


ACKNOWLEDGEMENTS

 * JimSRush with PrivSec Consulting
 * Metin Yunus Kandemir

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
Filters
Release date

Product

Platform

Impact

Max Severity

Article

Download

Build Number

Aug 8, 2024
Microsoft Office 2016 (64-bit edition)
-
Spoofing
Important
 * 5002625 
 * 5002570 

 * Security Update 
 * Security Update 

 * 16.0.5461.1001
 * 16.0.5461.1000

Aug 8, 2024
Microsoft Office 2016 (32-bit edition)
-
Spoofing
Important
 * 5002625 
 * 5002570 

 * Security Update 
 * Security Update 

 * 16.0.5461.1001
 * 16.0.5461.1000

Aug 8, 2024
Microsoft Office LTSC 2021 for 32-bit editions
-
Spoofing
Important
 * Click to Run 

 * Security Update

 * https://aka.ms/OfficeSecurityReleases

Aug 8, 2024
Microsoft Office LTSC 2021 for 64-bit editions
-
Spoofing
Important
 * Click to Run 

 * Security Update

 * https://aka.ms/OfficeSecurityReleases

Aug 8, 2024
Microsoft 365 Apps for Enterprise for 64-bit Systems
-
Spoofing
Important
 * Click to Run 

 * Security Update

 * https://aka.ms/OfficeSecurityReleases

Aug 8, 2024
Microsoft 365 Apps for Enterprise for 32-bit Systems
-
Spoofing
Important
 * Click to Run 

 * Security Update

 * https://aka.ms/OfficeSecurityReleases

Aug 8, 2024
Microsoft Office 2019 for 64-bit editions
-
Spoofing
Important
 * Click to Run 

 * Security Update

 * https://aka.ms/OfficeSecurityReleases

Aug 8, 2024
Microsoft Office 2019 for 32-bit editions
-
Spoofing
Important
 * Click to Run 

 * Security Update

 * https://aka.ms/OfficeSecurityReleases


All results loaded
Loaded all 8 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.2
Aug 10, 2024

Updated the Publicly Disclosed information.

1.1
Aug 9, 2024

Added FAQ information. This is an informational change only.

1.0
Aug 8, 2024

Information published.


How satisfied are you with the MSRC Security Update Guide?
Rating

Broken

Bad

Below average

Average

Great!
