Skip to content
Server Security Center
KEVmedium5.4

CVE-2024-38217: Microsoft Windows Mark of the Web (MOTW) Protection Mechanism Failure

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2024-09-10.

CVSS v3.1 (CVE record)
5.4
medium
EPSS (exploit probability, 30 days)
10%
higher than 95.7% of all CVEs
Added to CISA KEV
2024-09-10
US federal due date 2024-10-01
Automatable (CISA SSVC)
no
technical impact: partial

CVE-2024-38217 explained

CVE-2024-38217 is a protection mechanism failure in the Mark of the Web (MOTW) feature of Microsoft Windows. It lets an attacker bypass MOTW-based defenses, weakening security features such as Protected View in Microsoft Office that rely on MOTW tagging. CISA lists it as known exploited, so patching should be a priority.

Impact

An attacker can cause files to escape MOTW-based checks, so security features that depend on MOTW tagging may not apply. The attack works over the network, needs no privileges and has low complexity, but requires user interaction. The impact is limited to integrity and availability of these security features, with no direct confidentiality loss. CISA rates it not automatable with partial technical impact. Attackers are known to exploit it.

Who is affected

The CVE record lists Windows 10 versions 1507, 1607, 1809, 21H2 and 22H2, and Windows 11 versions 21H2, 22H2, 22H3, 23H2 and 24H2. It also lists Windows Server 2008 Service Pack 2 and Windows Server 2008 R2 Service Pack 1. Fixed builds include 10.0.19045.4894 (Windows 10 22H2), 10.0.22631.4169 (Windows 11 23H2), 10.0.26100.1742 (Windows 11 24H2) and 6.1.7601.27320 (Server 2008 R2 SP1). Further products are listed on this page.

Written with AI from the data on this page and checked against it automatically.

Official description

Microsoft Windows Mark of the Web (MOTW) contains a protection mechanism failure vulnerability that allows an attacker to bypass MOTW-based defenses. This can result in a limited loss of integrity and availability of security features such as Protected View in Microsoft Office, which rely on MOTW tagging.

CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    • < 10.0.10240.20766
    Fixed in
    • 10.0.10240.20766
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.7336
    Fixed in
    • 10.0.14393.7336
  • Microsoft Windows 10 Version 180932-bit, x64
    Affected
    • < 10.0.17763.6293
    Fixed in
    • 10.0.17763.6293
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.4894
    Fixed in
    • 10.0.19044.4894
  • Microsoft Windows 10 Version 22H232-bit, ARM64, x64
    Affected
    • < 10.0.19045.4894
    Fixed in
    • 10.0.19045.4894
  • Microsoft Windows 11 version 21H2ARM64, x64
    Affected
    • < 10.0.22000.3197
    Fixed in
    • 10.0.22000.3197
  • Microsoft Windows 11 version 22H2ARM64, x64
    Affected
    • < 10.0.22621.4169
    Fixed in
    • 10.0.22621.4169
  • Microsoft Windows 11 version 22H3ARM64
    Affected
    • < 10.0.22631.4169
    Fixed in
    • 10.0.22631.4169
  • Microsoft Windows 11 Version 23H2x64
    Affected
    • < 10.0.22631.4169
    Fixed in
    • 10.0.22631.4169
  • Microsoft Windows 11 Version 24H2ARM64, x64
    Affected
    • < 10.0.26100.1742
    Fixed in
    • 10.0.26100.1742
Show 14 more products
  • Microsoft Windows Server 2008 Service Pack 2x64, 32-bit
    Affected
    • < 6.0.6003.22870
    Fixed in
    • 6.0.6003.22870
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.27320
    Fixed in
    • 6.1.7601.27320
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.27320
    Fixed in
    • 6.1.7601.27320
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.22870
    Fixed in
    • 6.0.6003.22870
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.25073
    Fixed in
    • 6.2.9200.25073
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.25073
    Fixed in
    • 6.2.9200.25073
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.22175
    Fixed in
    • 6.3.9600.22175
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.22175
    Fixed in
    • 6.3.9600.22175
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.7336
    Fixed in
    • 10.0.14393.7336
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.7336
    Fixed in
    • 10.0.14393.7336
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.6293
    Fixed in
    • 10.0.17763.6293
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.6293
    Fixed in
    • 10.0.17763.6293
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.2700
    Fixed in
    • 10.0.20348.2700
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64
    Affected
    • < 10.0.25398.1128
    Fixed in
    • 10.0.25398.1128

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1507: 10.0.10240.20766
    • Microsoft Windows 10 Version 1607: 10.0.14393.7336
    • Microsoft Windows 10 Version 1809: 10.0.17763.6293
    • Microsoft Windows 10 Version 21H2: 10.0.19044.4894
    • Microsoft Windows 10 Version 22H2: 10.0.19045.4894
    • Microsoft Windows 11 version 21H2: 10.0.22000.3197
    Fixed versions for 18 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2024-38217
  • CISA's deadline for US federal agencies: 2024-10-01 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security update that brings each system to at least the fixed build listed for its Windows version.
  2. Prioritize patching because CISA lists this vulnerability as known exploited; the US federal due date was 2024-10-01.
  3. Follow the Microsoft vendor advisory for any additional mitigations or product-specific guidance.
  4. Warn users to be cautious with downloaded files and attachments, since exploitation requires user interaction.
  5. Check systems for signs of compromise, such as unexpected execution of files from untrusted sources.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Partial – limited control or information

Weakness: CWE-693 Protection Mechanism Failure

Questions about CVE-2024-38217

Is CVE-2024-38217 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2024-09-10. Whether it is used in ransomware campaigns is unknown.
Why does a medium-severity bug matter?
It weakens MOTW, which features such as Protected View in Microsoft Office rely on to treat files from untrusted sources with caution. Attackers are known to exploit it.
Which Windows 11 builds contain the fix?
Fixed builds are 10.0.22000.3197 for 21H2, 10.0.22621.4169 for 22H2, 10.0.22631.4169 for 22H3 and 23H2, and 10.0.26100.1742 for 24H2.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.