Windows Mark of the Web Security Feature Bypass Vulnerability
🔗 CVE IDs covered (1)
📋 Description
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 Protected View in Microsoft Office, which rely on MOTW tagging.
🎯 Affected products33
- Windows 10 Version 1607 for 32-bit Systems
- Windows 10 Version 1607 for x64-based Systems
- Windows 10 Version 1809 for 32-bit Systems
- Windows 10 Version 1809 for ARM64-based Systems
- Windows 10 Version 1809 for x64-based Systems
- Windows 10 Version 21H2 for 32-bit Systems
- Windows 10 Version 21H2 for ARM64-based Systems
- Windows 10 Version 21H2 for x64-based Systems
- Windows 10 Version 22H2 for 32-bit Systems
- Windows 10 Version 22H2 for ARM64-based Systems
- Windows 10 Version 22H2 for x64-based Systems
- Windows 10 for 32-bit Systems
- Windows 10 for x64-based Systems
- Windows 11 Version 22H2 for ARM64-based Systems
- Windows 11 Version 22H2 for x64-based Systems
- Windows 11 version 21H2 for ARM64-based Systems
- Windows 11 version 21H2 for x64-based Systems
- Windows Server 2008 R2 for x64-based Systems Service Pack 1
- Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)
- Windows Server 2008 for 32-bit Systems Service Pack 2
- Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)
- Windows Server 2008 for x64-based Systems Service Pack 2
- Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation)
- Windows Server 2012
- Windows Server 2012 (Server Core installation)
- Windows Server 2012 R2
- Windows Server 2012 R2 (Server Core installation)
- Windows Server 2016
- Windows Server 2016 (Server Core installation)
- Windows Server 2019
- +3 more not shown
✅ Remediation
KB5031361 (Security Update) — fixed build 10.0.17763.4974 KB5031364 (Security Update) — fixed build 10.0.20348.2031 KB5031358 (Security Update) — fixed build 10.0.22000.2538 KB5031356 (Security Update) — fixed build 10.0.19041.3570 KB5031354 (Security Update) — fixed build 10.0.22621.2428 KB5031356 (Security Update) — fixed build 10.0.19045.3570 KB5031377 (Security Update) — fixed build 10.0.10240.20232 KB5031362 (Security Update) — fixed build 10.0.14393.6351 KB5031416 (Monthly Rollup) — fixed build 6.0.6003.22317 KB5031411 (Security Only) — fixed build 6.0.6003.22317 KB5031408 (Monthly Rollup) — fixed build 6.1.7601.26769 KB5031441 (Security Only) — fixed build 6.1.7601.26769 KB5031442 (Monthly Rollup) — fixed build 6.2.9200.24523 KB5031427 (Security Only) — fixed build 6.2.9200.24523 KB5031419 (Monthly Rollup) — fixed build 6.3.9600.21620 KB5031407 (Security Only) — fixed build 6.3.9600.21620
🔗 References (36)
- advisoryhttps://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-36584
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5031361
- referencehttps://support.microsoft.com/help/5031361
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5031364
- referencehttps://support.microsoft.com/help/5031364
- referencehttp://support.microsoft.com/help/5031364
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5031358
- referencehttps://support.microsoft.com/help/5031358
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5031356
- referencehttps://support.microsoft.com/help/5031356
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5031354
- referencehttps://support.microsoft.com/help/5031354
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5031377
- referencehttps://support.microsoft.com/help/5031377
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5031362
- referencehttps://support.microsoft.com/help/5031362
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5031416
- referencehttps://support.microsoft.com/help/5031416
- referencehttp://support.microsoft.com/kb/5031416
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5031411
- referencehttps://support.microsoft.com/help/5031411
- referencehttp://support.microsoft.com/kb/5031411
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5031408
- referencehttps://support.microsoft.com/help/5031408
- referencehttp://support.microsoft.com/kb/5031408
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5031441
- referencehttps://support.microsoft.com/help/5031441
- referencehttp://support.microsoft.com/kb/5031441
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5031442
- referencehttps://support.microsoft.com/help/5031442
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5031427
- referencehttps://support.microsoft.com/help/5031427
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5031419
- referencehttps://support.microsoft.com/help/5031419
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5031407
- referencehttps://support.microsoft.com/help/5031407