CVE-2023-36884: Windows Search Remote Code Execution Vulnerability

Published Jul 11, 2023
·
Updated

Microsoft is investigating reports of a series of remote code execution vulnerabilities impacting Windows and Office products. Microsoft is aware of targeted attacks that attempt to exploit these vulnerabilities by using specially-crafted Microsoft Office documents.

An attacker could create a specially crafted Microsoft Office document that enables them to perform remote code execution in the context of the victim. However, an attacker would have to convince the victim to open the malicious file.

Upon completion of this investigation, Microsoft will take the appropriate action to help protect our customers. This might include providing a security update through our monthly release process or providing an out-of-cycle security update, depending on customer needs.

Please see the Microsoft Threat Intelligence Blog https://aka.ms/Storm-0978  Entry for important information about steps you can take to protect your system from this vulnerability.

This CVE will be updated with new information and links to security updates when they become available.

Other sources

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

Windows Search Remote Code Execution Vulnerability

Microsoft

Affected Software

104 affected componentsFixes available
Microsoft Word 2016
Microsoft Word 2016
Microsoft Word 2013
Microsoft Word 2013
Microsoft Office 2019 for 32-bit editions
Microsoft Office LTSC 2021 for 64-bit editions
Microsoft Office 2019 for 64-bit editions
Microsoft Office LTSC 2021 for 32-bit editions
Microsoft Windows Server 2019
Microsoft Windows Server 2019
Microsoft Windows 11=22H2
Microsoft Windows 11=22H2
Microsoft Windows 11=21H2
Microsoft Windows 11=21H2
Microsoft Windows Server 2022
Microsoft Windows Server 2022
Microsoft Office=2019
Microsoft Office=2019
Microsoft Office=2021
Microsoft Office=2021
Microsoft Word=2013-sp1
Microsoft Word=2016
Microsoft Windows 10 1507
Microsoft Windows 10 1507
Microsoft Windows 10 1607
Microsoft Windows 10 1607
Microsoft Windows 10 1809
Microsoft Windows 10 1809
Microsoft Windows 10 1809
Microsoft Windows 10 21h2
Microsoft Windows 10 21h2
Microsoft Windows 10 21h2
Microsoft Windows 10 22h2
Microsoft Windows 10 22h2
Microsoft Windows 10 22h2
Microsoft Windows 11=22h2
Microsoft Windows 11=22h2
Microsoft Windows 11 21h2
Microsoft Windows 11 21h2
Microsoft Windows Server 2008=sp2
Microsoft Windows Server 2008=r2-sp1
Microsoft Windows Server 2012
Microsoft Windows Server 2012=r2
Microsoft Windows Server 2016
Microsoft Windows Server 2019
Microsoft Windows Server 2022
Microsoft Windows 10=1809
Microsoft Windows 10=1809
Microsoft Windows 10=1809
Microsoft Windows 10=22H2
Microsoft Windows 10=22H2
Microsoft Windows 10=22H2
Microsoft Windows 10=21H2
Microsoft Windows 10=21H2
Microsoft Windows 10=21H2
Microsoft Windows 10
Microsoft Windows 10
Microsoft Windows
Microsoft Windows 10 1507<10.0.10240.20107
Microsoft Windows 10 1607<10.0.14393.6167
Microsoft Windows 10 1607<10.0.14393.6167
Microsoft Windows 10 1809<10.0.17763.4737
Microsoft Windows 10 1809<10.0.17763.4737
Microsoft Windows 10 1809<10.0.17763.4737
Microsoft Windows 10 21h2<10.0.19044.3324
Microsoft Windows 10 22h2<10.0.19044.3324
Microsoft Windows 11 21h2<10.0.22000.2295
Microsoft Windows 11 22h2<10.0.22621.2134
Microsoft Windows Server 2016<10.0.14393.6167
Microsoft Windows Server 2019<10.0.17763.4737
Microsoft Windows Server 2022<10.0.20348.1903
Microsoft Windows 10<10.0.10240.20107
10.0.10240.20107
Microsoft Windows 10<10.0.10240.20107
10.0.10240.20107
Microsoft Windows 10=22H2
10.0.19044.3324
Microsoft Windows 11=22H2
10.0.22621.2134
Microsoft Windows 10=21H2
10.0.19044.3324
Microsoft Windows 10=21H2
10.0.19044.3324
Microsoft Windows 11=22H2
10.0.22621.2134
Microsoft Windows 10=22H2
10.0.19045.3324
Microsoft Windows 10=22H2
10.0.19045.3324
Microsoft Windows 11=21H2
10.0.22000.2295
Microsoft Windows 10=21H2
10.0.19044.3324
Microsoft Windows 11=21H2
10.0.22000.2295
Microsoft Windows Server 2022<10.0.20348.1906, <10.0.20348.1903
10.0.20348.190610.0.20348.1903
Microsoft Windows Server 2022<10.0.20348.1906, <10.0.20348.1903
10.0.20348.190610.0.20348.1903
Microsoft Windows Server 2019<10.0.17763.4737
10.0.17763.4737
Microsoft Windows 10=1809
10.0.17763.4737
Microsoft Windows Server 2019<10.0.17763.4737
10.0.17763.4737
Microsoft Windows 10=1809
10.0.17763.4737
Microsoft Windows 10=1809
10.0.17763.4737
Microsoft Windows Server 2012<6.2.9200.24414
6.2.9200.24414
Microsoft Windows Server 2008 R2<6.1.7601.26664
6.1.7601.26664
Microsoft Windows Server 2008<6.0.6003.22216
6.0.6003.22216
Microsoft Windows Server 2008<6.0.6003.22216
6.0.6003.22216
Microsoft Windows Server 2008 R2<6.1.7601.26664
6.1.7601.26664
Microsoft Windows Server 2008<6.0.6003.22216
6.0.6003.22216
Microsoft Windows Server 2016<10.0.14393.6167
10.0.14393.6167
Microsoft Windows Server 2008<6.0.6003.22216
6.0.6003.22216
Microsoft Windows 10=1607
10.0.14393.6167
Microsoft Windows 10=1607
10.0.14393.6167
Microsoft Windows Server 2016<10.0.14393.6167
10.0.14393.6167
Microsoft Windows Server 2012<6.2.9200.24414
6.2.9200.24414
Microsoft Windows Server 2012 R2<6.3.9600.21503
6.3.9600.21503
Microsoft Windows Server 2012 R2<6.3.9600.21503
6.3.9600.21503

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 10.0.10240.20107Patch KB5029259
  2. Upgrade

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

    Fixed in 10.0.19044.3324Patch KB5029244
  3. Upgrade

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

    Fixed in 10.0.22621.2134Patch KB5029263
  4. Upgrade

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

    Fixed in 10.0.19045.3324Patch KB5029244
  5. Upgrade

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

    Fixed in 10.0.22000.2295Patch KB5029253
  6. Upgrade

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

    Fixed in 10.0.20348.1906Fixed in 10.0.20348.1903Patch KB5029367
  7. Upgrade

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

    Fixed in 10.0.17763.4737Patch KB5029247
  8. Upgrade

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

    Fixed in 6.2.9200.24414Patch KB5029308
  9. Upgrade

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

    Fixed in 6.1.7601.26664Patch KB5029307
  10. Upgrade

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

    Fixed in 6.0.6003.22216Patch KB5029301
  11. Upgrade

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

    Fixed in 10.0.14393.6167Patch KB5029242
  12. Upgrade

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

    Fixed in 6.3.9600.21503Patch KB5029304

Event History

Jul 11, 2023
CVE Published
07:00 AM
Known Exploited
via Microsoft·07: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·06:14 PM
Data Sourced
via MITRE·06:14 PM
DescriptionSeverity
Data Sourced
via NVD·07:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jul 17, 2023
Known Ransomware
via CISA·12:00 AM
Oct 10, 2024
News Published
via BleepingComputer·04:00 PM
News Published
via BleepingComputer·04:01 PM
Nov 26, 2024
News Published
via BleepingComputer·12:13 PM
Dec 1, 2024
News Published
via The Register·08:24 PM
News Published
via The Register·08:27 PM
Aug 11, 2025
News Published
via BleepingComputer·06:05 PM
News Published
via The Register·07:08 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2023-36884?

CVE-2023-36884 is classified as a critical vulnerability due to its potential for remote code execution.

2

How do I fix CVE-2023-36884?

To remediate CVE-2023-36884, users should apply the latest security patches provided by Microsoft.

3

What products are affected by CVE-2023-36884?

CVE-2023-36884 impacts multiple Microsoft products including various versions of Windows and Microsoft Office.

4

Are there any known exploits for CVE-2023-36884?

Yes, there are reports of targeted attacks that exploit CVE-2023-36884 using specially-crafted Microsoft Office documents.

5

How can I tell if I am affected by CVE-2023-36884?

Users can determine if they are affected by CVE-2023-36884 by checking their version of Microsoft Office or Windows against the list of affected products.

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