CVE-2023-36884: Microsoft Windows Search Remote Code Execution
Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2023-07-17.
- CVSS v3.1 (CVE record)
- 7.5
- high
- EPSS (exploit probability, 30 days)
- 99.4%
- among the highest 0.1% of all CVEs
- Added to CISA KEV
- 2023-07-17
- US federal due date 2023-08-29
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2023-36884 explained
CVE-2023-36884 is a vulnerability in Microsoft Windows Search that can let an attacker evade Mark of the Web (MOTW) defenses with a specially crafted malicious file, leading to remote code execution. CISA lists it as known exploited, with known ransomware use, and it affects a wide range of Windows client and server versions.
Impact
An attacker who gets a user to open a crafted file can bypass MOTW protections and run code remotely. No privileges are needed, but user interaction is required and attack complexity is high. Successful exploitation affects confidentiality, integrity and availability. CISA rates the technical impact as total but not automatable. Attackers are known to use it, including in ransomware campaigns.
Who is affected
The CVE record lists Windows 10 versions 1507, 1607, 1809, 21H2 and 22H2. It also lists Windows 11 versions 21H2 and 22H2, Windows Server 2008 SP2 and 2008 R2 SP1 (including Server Core installations) and Windows Server 2012. Fixed builds include 10.0.19045.3324 (Windows 10 22H2), 10.0.22621.2134 (Windows 11 22H2), 6.2.9200.24414 (Server 2012) and 6.1.7601.26664 (Server 2008 R2 SP1). Each product's fixed build is shown in the table. Further products are listed on the page.
Written with AI from the data on this page and checked against it automatically.
Official description
Microsoft Windows Search contains an unspecified vulnerability that could allow an attacker to evade Mark of the Web (MOTW) defenses via a specially crafted malicious file, leading to remote code execution.
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, x64AffectedFixed in
- < 10.0.10240.20107
- 10.0.10240.20107
- Microsoft Windows 10 Version 160732-bit, x64AffectedFixed in
- < 10.0.14393.6167
- 10.0.14393.6167
- Microsoft Windows 10 Version 180932-bit, x64, ARM64AffectedFixed in
- < 10.0.17763.4737
- 10.0.17763.4737
- Microsoft Windows 10 Version 21H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19044.3324
- 10.0.19044.3324
- Microsoft Windows 10 Version 22H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19045.3324
- 10.0.19045.3324
- Microsoft Windows 11 version 21H2ARM64, x64AffectedFixed in
- < 10.0.22000.2295
- 10.0.22000.2295
- Microsoft Windows 11 version 22H2ARM64, x64AffectedFixed in
- < 10.0.22621.2134
- 10.0.22621.2134
- Microsoft Windows Server 2008 Service Pack 2x64, 32-bitAffectedFixed in
- < 6.0.6003.22216
- 6.0.6003.22216
- Microsoft Windows Server 2008 R2 Service Pack 1x64AffectedFixed in
- < 6.1.7601.26664
- 6.1.7601.26664
- Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64AffectedFixed in
- < 6.1.7601.26664
- 6.1.7601.26664
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 10 Version 150732-bit, x64 |
|
|
| Microsoft Windows 10 Version 160732-bit, x64 |
|
|
| Microsoft Windows 10 Version 180932-bit, x64, ARM64 |
|
|
| Microsoft Windows 10 Version 21H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 10 Version 22H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 11 version 21H2ARM64, x64 |
|
|
| Microsoft Windows 11 version 22H2ARM64, x64 |
|
|
| Microsoft Windows Server 2008 Service Pack 2x64, 32-bit |
|
|
| Microsoft Windows Server 2008 R2 Service Pack 1x64 |
|
|
| Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64 |
|
|
Show 10 more products
- Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64AffectedFixed in
- < 6.0.6003.22216
- 6.0.6003.22216
- Microsoft Windows Server 2012x64AffectedFixed in
- < 6.2.9200.24414
- 6.2.9200.24414
- Microsoft Windows Server 2012 (Server Core installation)x64AffectedFixed in
- < 6.2.9200.24414
- 6.2.9200.24414
- Microsoft Windows Server 2012 R2x64AffectedFixed in
- < 6.3.9600.21503
- 6.3.9600.21503
- Microsoft Windows Server 2012 R2 (Server Core installation)x64AffectedFixed in
- < 6.3.9600.21503
- 6.3.9600.21503
- Microsoft Windows Server 2016x64AffectedFixed in
- < 10.0.14393.6167
- 10.0.14393.6167
- Microsoft Windows Server 2016 (Server Core installation)x64AffectedFixed in
- < 10.0.14393.6167
- 10.0.14393.6167
- Microsoft Windows Server 2019x64AffectedFixed in
- < 10.0.17763.4737
- 10.0.17763.4737
- Microsoft Windows Server 2019 (Server Core installation)x64AffectedFixed in
- < 10.0.17763.4737
- 10.0.17763.4737
- Microsoft Windows Server 2022x64AffectedFixed in
- < 10.0.20348.1906
- 10.0.20348.1906
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64 |
|
|
| Microsoft Windows Server 2012x64 |
|
|
| Microsoft Windows Server 2012 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2012 R2x64 |
|
|
| Microsoft Windows Server 2012 R2 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2016x64 |
|
|
| Microsoft Windows Server 2016 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2019x64 |
|
|
| Microsoft Windows Server 2019 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2022x64 |
|
|
How to fix it
- Update to the fixed version for your product:
- Microsoft Windows 10 Version 1507: 10.0.10240.20107
- Microsoft Windows 10 Version 1607: 10.0.14393.6167
- Microsoft Windows 10 Version 1809: 10.0.17763.4737
- Microsoft Windows 10 Version 21H2: 10.0.19044.3324
- Microsoft Windows 10 Version 22H2: 10.0.19045.3324
- Microsoft Windows 11 version 21H2: 10.0.22000.2295
- Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2023-36884
- CISA's deadline for US federal agencies: 2023-08-29 (passed) – a useful benchmark for everyone else, too.
What to do
- Install the Windows updates that bring each system to the fixed build listed for its product, for example
10.0.22621.2134for Windows 11 version 22H2. - Apply mitigations per Microsoft's instructions, as CISA's required action states. If mitigations are unavailable, discontinue use of the product.
- Prioritize patching, because CISA lists this vulnerability as known exploited with known ransomware use.
- Treat files from untrusted sources with caution and reinforce user awareness, since exploitation requires user interaction.
- Check systems for signs of compromise, especially unpatched hosts that handled untrusted files.
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
- Total – full control of the component or total information disclosure
Weakness: CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Questions about CVE-2023-36884
- Is CVE-2023-36884 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2023-07-17 and notes known ransomware use. The US federal due date was 2023-08-29.
- Can it be exploited without user action?
- No. The CVSS vector requires user interaction, such as opening a specially crafted file, and the attack complexity is high. CISA also rates it as not automatable.
- What should I do if I cannot patch immediately?
- Follow CISA's required action. Apply mitigations per Microsoft's instructions, or discontinue use of the product if mitigations are unavailable.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
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.