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

 1. MSRC
    MSRC
    
 2. Customer Guidance
    Customer Guidance
    
 3. Security Update Guide
    Security Update Guide
    
 4. Vulnerabilities
    Vulnerabilities
    
 5. CVE 2024 38217
    CVE 2024 38217


WINDOWS MARK OF THE WEB SECURITY FEATURE BYPASS VULNERABILITY NEW

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

Released: Sep 9, 2024

Assigning CNA:
Microsoft

CVE-2024-38217 

Impact: Security Feature Bypass

Max Severity: Important

Weakness:
CWE-693: Protection Mechanism Failure
CVSS Source: Microsoft
CVSS:3.1 5.4 / 5.0
Base score metrics: 5.4 / Temporal score metrics: 5.0
Base score metrics: 5.4 / Temporal score metrics: 5.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.
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.
None
There is no loss of confidentiality within the impacted component.
Integrity
This metric measures the impact to integrity of a successfully exploited
vulnerability. Integrity refers to the trustworthiness and veracity of
information.
Low
Modification of data is possible, but the attacker does not have control over
the consequence of a modification, or the amount of modification is limited. The
data modification does not have a direct, serious impact on 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.
Low
Performance is reduced or there are interruptions in resource availability. Even
if repeated exploitation of the vulnerability is possible, the attacker does not
have the ability to completely deny service to legitimate users. The resources
in the impacted component are either partially available all of the time, or
fully available only some of the time, but overall there is no direct, serious
consequence to 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.
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.
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 disclosedYesExploitedYesExploitability assessmentExploitation Detected


FAQ

How could an attacker exploit the vulnerability?

To exploit this vulnerability, an attacker could host a file on an
attacker-controlled server, then convince a targeted user to download and open
the file. This could allow the attacker to interfere with the Mark of the Web
functionality.

Please see Additional information about Mark of the Web for further
clarification

According to the CVSS metric, successful exploitation of this vulnerability
could lead to some loss of integrity (I:L) and some loss of availability (A:L).
What does that mean for this vulnerability?

An attacker can craft a malicious file that would evade Mark of the Web (MOTW)
defenses, resulting in a limited loss of integrity and availability of security
features such as SmartScreen Application Reputation security check and/or the
legacy Windows Attachment Services security prompt.

Windows 11, version 24H2 is not generally available yet. Why are there updates
for this version of Windows listed in the Security Updates table?

The new Copilot+ devices that are now publicly available come with Windows 11,
version 24H2 installed. Customers with these devices need to know about any
vulnerabilities that affect their machine and to install the updates if they are
not receiving automatic updates. Note that the general availability date for
Windows 11, version 24H2 is scheduled for later this year.


ACKNOWLEDGEMENTS

 * Joe Desimone with Elastic Security

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

Sep 9, 2024
Windows Server 2012 R2
-
Security Feature Bypass
Important
 * 5043138 

 * Monthly Rollup 

 * 6.3.9600.22175

Sep 9, 2024
Windows Server 2012 (Server Core installation)
-
Security Feature Bypass
Important
 * 5043125 

 * Monthly Rollup 

 * 6.2.9200.25073

Sep 9, 2024
Windows Server 2012
-
Security Feature Bypass
Important
 * 5043125 

 * Monthly Rollup 

 * 6.2.9200.25073

Sep 9, 2024
Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core
installation)
-
Security Feature Bypass
Important
 * 5043129 
 * 5043092 

 * Monthly Rollup 
 * Security Only 

 * 6.1.7601.27320
 * 6.1.7601.27320

Sep 9, 2024
Windows Server 2008 R2 for x64-based Systems Service Pack 1
-
Security Feature Bypass
Important
 * 5043129 
 * 5043092 

 * Monthly Rollup 
 * Security Only 

 * 6.1.7601.27320
 * 6.1.7601.27320

Sep 9, 2024
Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core
installation)
-
Security Feature Bypass
Important
 * 5043135 
 * 5043087 

 * Monthly Rollup 
 * Security Only 

 * 6.0.6003.22870
 * 6.0.6003.22870

Sep 9, 2024
Windows Server 2008 for x64-based Systems Service Pack 2
-
Security Feature Bypass
Important
 * 5043135 
 * 5043087 

 * Monthly Rollup 
 * Security Only 

 * 6.0.6003.22870
 * 6.0.6003.22870

Sep 9, 2024
Windows Server 2012 R2 (Server Core installation)
-
Security Feature Bypass
Important
 * 5043138 

 * Monthly Rollup 

 * 6.3.9600.22175

Sep 9, 2024
Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)
-
Security Feature Bypass
Important
 * 5043135 
 * 5043087 

 * Monthly Rollup 
 * Security Only 

 * 6.0.6003.22870
 * 6.0.6003.22870

Sep 9, 2024
Windows Server 2008 for 32-bit Systems Service Pack 2
-
Security Feature Bypass
Important
 * 5043135 
 * 5043087 

 * Monthly Rollup 
 * Security Only 

 * 6.0.6003.22870
 * 6.0.6003.22870

Sep 9, 2024
Windows Server 2016 (Server Core installation)
-
Security Feature Bypass
Important
 * 5043051 

 * Security Update 

 * 10.0.14393.7336

Sep 9, 2024
Windows Server 2016
-
Security Feature Bypass
Important
 * 5043051 

 * Security Update 

 * 10.0.14393.7336

Sep 9, 2024
Windows 10 Version 1607 for x64-based Systems
-
Security Feature Bypass
Important
 * 5043051 

 * Security Update 

 * 10.0.14393.7336

Sep 9, 2024
Windows 10 Version 1607 for 32-bit Systems
-
Security Feature Bypass
Important
 * 5043051 

 * Security Update 

 * 10.0.14393.7336

Sep 9, 2024
Windows 10 for x64-based Systems
-
Security Feature Bypass
Important
 * 5043083 

 * Security Update 

 * 10.0.10240.20766

Sep 9, 2024
Windows 10 for 32-bit Systems
-
Security Feature Bypass
Important
 * 5043083 

 * Security Update 

 * 10.0.10240.20766

Sep 9, 2024
Windows 11 Version 24H2 for x64-based Systems
-
Security Feature Bypass
Important
 * 5043080 

 * Security Update 

 * 10.0.26100.1742

Sep 9, 2024
Windows 11 Version 24H2 for ARM64-based Systems
-
Security Feature Bypass
Important
 * 5043080 

 * Security Update 

 * 10.0.26100.1742

Sep 9, 2024
Windows Server 2022, 23H2 Edition (Server Core installation)
-
Security Feature Bypass
Important
 * 5043055 

 * Security Update 

 * 10.0.25398.1128

Sep 9, 2024
Windows 11 Version 23H2 for x64-based Systems
-
Security Feature Bypass
Important
 * 5043076 

 * Security Update 

 * 10.0.22631.4169

Sep 9, 2024
Windows 11 Version 23H2 for ARM64-based Systems
-
Security Feature Bypass
Important
 * 5043076 

 * Security Update 

 * 10.0.22631.4169

Sep 9, 2024
Windows 10 Version 22H2 for 32-bit Systems
-
Security Feature Bypass
Important
 * 5043064 

 * Security Update 

 * 10.0.19045.4894

Sep 9, 2024
Windows 10 Version 22H2 for ARM64-based Systems
-
Security Feature Bypass
Important
 * 5043064 

 * Security Update 

 * 10.0.19045.4894

Sep 9, 2024
Windows 10 Version 22H2 for x64-based Systems
-
Security Feature Bypass
Important
 * 5043064 

 * Security Update 

 * 10.0.19045.4894

Sep 9, 2024
Windows 11 Version 22H2 for x64-based Systems
-
Security Feature Bypass
Important
 * 5043076 

 * Security Update 

 * 10.0.22621.4169

Sep 9, 2024
Windows 11 Version 22H2 for ARM64-based Systems
-
Security Feature Bypass
Important
 * 5043076 

 * Security Update 

 * 10.0.22621.4169

Sep 9, 2024
Windows 10 Version 21H2 for x64-based Systems
-
Security Feature Bypass
Important
 * 5043064 

 * Security Update 

 * 10.0.19044.4894

Sep 9, 2024
Windows 10 Version 21H2 for ARM64-based Systems
-
Security Feature Bypass
Important
 * 5043064 

 * Security Update 

 * 10.0.19044.4894

Sep 9, 2024
Windows 10 Version 21H2 for 32-bit Systems
-
Security Feature Bypass
Important
 * 5043064 

 * Security Update 

 * 10.0.19044.4894

Sep 9, 2024
Windows 11 version 21H2 for ARM64-based Systems
-
Security Feature Bypass
Important
 * 5043067 

 * Security Update 

 * 10.0.22000.3197

Sep 9, 2024
Windows 11 version 21H2 for x64-based Systems
-
Security Feature Bypass
Important
 * 5043067 

 * Security Update 

 * 10.0.22000.3197

Sep 9, 2024
Windows Server 2022 (Server Core installation)
-
Security Feature Bypass
Important
 * 5042881 
 * 5042880 

 * Security Update 
 * SecurityHotpatchUpdate 

 * 10.0.20348.2700
 * 10.0.20348.2695

Sep 9, 2024
Windows Server 2022
-
Security Feature Bypass
Important
 * 5042881 
 * 5042880 

 * Security Update 
 * SecurityHotpatchUpdate 

 * 10.0.20348.2700
 * 10.0.20348.2695

Sep 9, 2024
Windows Server 2019 (Server Core installation)
-
Security Feature Bypass
Important
 * 5043050 

 * Security Update 

 * 10.0.17763.6293

Sep 9, 2024
Windows Server 2019
-
Security Feature Bypass
Important
 * 5043050 

 * Security Update 

 * 10.0.17763.6293

Sep 9, 2024
Windows 10 Version 1809 for ARM64-based Systems
-
Security Feature Bypass
Important
 * 5043050 

 * Security Update 

 * 10.0.17763.6293

Sep 9, 2024
Windows 10 Version 1809 for x64-based Systems
-
Security Feature Bypass
Important
 * 5043050 

 * Security Update 

 * 10.0.17763.6293

Sep 9, 2024
Windows 10 Version 1809 for 32-bit Systems
-
Security Feature Bypass
Important
 * 5043050 

 * Security Update 

 * 10.0.17763.6293


All results loaded
Loaded all 38 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.0
Sep 9, 2024

Information published.

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