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

Published Sep 10, 2024
·
Updated

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.

Other sources

Windows Mark of the Web Security Feature Bypass Vulnerability

Microsoft

Affected Software

67 affected componentsFixes available
Microsoft Windows Server 2012 R2
Microsoft Windows Server 2012
Microsoft Windows Server 2012
Microsoft Windows Server 2008
Microsoft Windows Server 2008
Microsoft Windows 10=1809
Microsoft Windows
Microsoft Windows Server 2008 R2
Microsoft Windows Server 2008 R2
Microsoft Windows 10 1507<10.0.10240.20766
Microsoft Windows 10 1507<10.0.10240.20766
Microsoft Windows 10 1607<10.0.14393.7336
Microsoft Windows 10 1607<10.0.14393.7336
Microsoft Windows 10 1809<10.0.17763.6293
Microsoft Windows 10 1809<10.0.17763.6293
Microsoft Windows 10 21h2<10.0.19044.4894
Microsoft Windows 10 22h2<10.0.19045.4894
Microsoft Windows 11 21h2<10.0.22000.3197
Microsoft Windows 11 22h2<10.0.22621.4169
Microsoft Windows 11 23h2<10.0.22631.4169
Microsoft Windows 11 24h2<10.0.26100.1742
Microsoft Windows 11 24h2<10.0.26100.1742
Microsoft Windows Server 2008=sp2
Microsoft Windows Server 2008=r2-sp1
Microsoft Windows Server 2012
Microsoft Windows Server 2012=r2
Microsoft Windows Server 2016<10.0.14393.7336
Microsoft Windows Server 2019<10.0.17763.6293
Microsoft Windows Server 2022<10.0.20348.2700
Microsoft Windows Server 2022 23h2<10.0.25398.1128
Microsoft Windows Server 2008 R2<6.1.7601.27320
6.1.7601.27320
Microsoft Windows Server 2012<6.2.9200.25073
6.2.9200.25073
Microsoft Windows Server 2008 R2<6.1.7601.27320
6.1.7601.27320
Microsoft Windows Server 2012 R2<6.3.9600.22175
6.3.9600.22175
Microsoft Windows Server 2008<6.0.6003.22870
6.0.6003.22870
Microsoft Windows Server 2008<6.0.6003.22870
6.0.6003.22870
Microsoft Windows Server 2012<6.2.9200.25073
6.2.9200.25073
Microsoft Windows Server 2016<10.0.14393.7336
10.0.14393.7336
Microsoft Windows 10=1607
10.0.14393.7336
Microsoft Windows Server 2008<6.0.6003.22870
6.0.6003.22870
Microsoft Windows Server 2012 R2<6.3.9600.22175
6.3.9600.22175
Microsoft Windows Server 2008<6.0.6003.22870
6.0.6003.22870
Microsoft Windows 10<10.0.10240.20766
10.0.10240.20766
Microsoft Windows Server 2016<10.0.14393.7336
10.0.14393.7336
Microsoft Windows 11=24H2
10.0.26100.1742
Microsoft Windows 10=1607
10.0.14393.7336
Microsoft Windows 11=23H2
10.0.22631.4169
Microsoft Windows 11=24H2
10.0.26100.1742
Microsoft Windows 11=23H2
10.0.22631.4169
Microsoft Windows Server 2022, 23H2 Edition<10.0.25398.1128
10.0.25398.1128
Microsoft Windows 10<10.0.10240.20766
10.0.10240.20766
Microsoft Windows 10=22H2
10.0.19045.4894
Microsoft Windows 10=22H2
10.0.19045.4894
Microsoft Windows 10=22H2
10.0.19045.4894
Microsoft Windows 11=22H2
10.0.22621.4169
Microsoft Windows 11=22H2
10.0.22621.4169
Microsoft Windows 10=21H2
10.0.19044.4894
Microsoft Windows 10=21H2
10.0.19044.4894
Microsoft Windows 11=21H2
10.0.22000.3197
Microsoft Windows 11=21H2
10.0.22000.3197
Microsoft Windows 10=21H2
10.0.19044.4894
Microsoft Windows Server 2022<10.0.20348.2700, <10.0.20348.2695
10.0.20348.270010.0.20348.2695
Microsoft Windows Server 2022<10.0.20348.2700, <10.0.20348.2695
10.0.20348.270010.0.20348.2695
Microsoft Windows Server 2019<10.0.17763.6293
10.0.17763.6293
Microsoft Windows 10=1809
10.0.17763.6293
Microsoft Windows 10=1809
10.0.17763.6293
Microsoft Windows Server 2019<10.0.17763.6293
10.0.17763.6293

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.1.7601.27320Patch KB5043092
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.3.9600.22175Patch KB5043138
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.2.9200.25073Patch KB5043125
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.0.6003.22870Patch KB5043087
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.14393.7336Patch KB5043051
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.10240.20766Patch KB5043083
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26100.1742Patch KB5043080
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.22631.4169Patch KB5043076
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.25398.1128Patch KB5043055
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19045.4894Patch KB5043064
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.22621.4169Patch KB5043076
  12. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19044.4894Patch KB5043064
  13. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.22000.3197Patch KB5043067
  14. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.20348.2700Fixed in 10.0.20348.2695Patch KB5042880
  15. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.17763.6293Patch KB5043050

Event History

Sep 10, 2024
CVE Published
via CISA·12:00 AM
Known Exploited
via CISA·12:00 AM
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
Description
CVE Published
via MITRE·04:53 PM
Data Sourced
via MITRE·04:53 PM
DescriptionSeverity
Data Sourced
via NVD·05:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Sep 15, 2024
News Published
via BleepingComputer·06:16 PM
News Published
via BleepingComputer·06:18 PM
Sep 16, 2024
News Published
via BleepingComputer·07:53 PM

Frequently Asked Questions

1

What is the severity of CVE-2024-38217?

CVE-2024-38217 has been rated with a moderate severity level due to its impact on the integrity and availability of security features like Protected View.

2

How do I fix CVE-2024-38217?

To fix CVE-2024-38217, it is recommended to apply the latest security patches provided by Microsoft for the affected versions of Windows.

3

Which versions of Windows are affected by CVE-2024-38217?

CVE-2024-38217 affects multiple versions of Windows, including Windows 10, Windows Server 2016, Windows Server 2019, Windows 11, and Windows Server 2022.

4

What type of vulnerability is CVE-2024-38217?

CVE-2024-38217 is classified as a protection mechanism failure vulnerability that allows attackers to bypass Mark of the Web-based defenses.

5

What are the potential impacts of CVE-2024-38217?

The potential impacts of CVE-2024-38217 include a limited loss of integrity and availability of security features in Microsoft Office applications.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203