Microsoft Windows Support Diagnostic Tool (MSDT) Remote Code Execution Vulnerability
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- Fix
- Fixed in 10.0.17763.3046, 10.0.19043.1766, 10.0.20348.770, 10.0.19042.1766, 10.0.22000.739, and 6 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Microsoft Windows Support Diagnostic Tool (MSDT) is affected, along with applications such as Microsoft Word that can call it through a URL protocol. An attacker who successfully exploits this flaw could run arbitrary code with the calling application's privileges, allowing them to install programs, access or alter data, or create accounts within the user's rights.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
A remote code execution vulnerability exists when MSDT is called using the URL protocol from a calling application such as Word. An attacker who successfully exploits this vulnerability can run arbitrary code with the privileges of the calling application. The attacker can then install programs, view, change, or delete data, or create new accounts in the context allowed by the user’s rights. Please see the MSRC Blog Entry for important information about steps you can take to protect your system from this vulnerability.
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- Microsoft Windows 10 Version 1809
From 10.0.17763.0 · fixed in 10.0.17763.3046
- Microsoft Windows 10 Version 1809
From 10.0.0 · fixed in 10.0.17763.3046
- Microsoft Windows Server 2019
From 10.0.17763.0 · fixed in 10.0.17763.3046
- Microsoft Windows Server 2019 (Server Core installation)
From 10.0.17763.0 · fixed in 10.0.17763.3046
- Microsoft Windows 10 Version 21H1
From 10.0.0 · fixed in 10.0.19043.1766
- Microsoft Windows Server 2022
From 10.0.20348.0 · fixed in 10.0.20348.770
- Microsoft Windows 10 Version 20H2
From 10.0.0 · fixed in 10.0.19042.1766
- Microsoft Windows Server version 20H2
From 10.0.0 · fixed in 10.0.19042.1766
- Microsoft Windows 11 version 21H2
From 10.0.0 · fixed in 10.0.22000.739
- Microsoft Windows 10 Version 21H2
From 10.0.19043.0 · fixed in 10.0.19044.1766
- Microsoft Windows 10 Version 1507
From 10.0.10240.0 · fixed in 10.0.10240.19325
- Microsoft Windows 10 Version 1607
From 10.0.14393.0 · fixed in 10.0.14393.5192
- Microsoft Windows Server 2016
From 10.0.14393.0 · fixed in 10.0.14393.5192
- Microsoft Windows Server 2016 (Server Core installation)
From 10.0.14393.0 · fixed in 10.0.14393.5192
- Microsoft Windows 7
From 6.1.0 · fixed in 6.1.7601.25984
- Microsoft Windows 7 Service Pack 1
From 6.1.0 · fixed in 6.1.7601.25984
- Microsoft Windows 8.1
From 6.3.0 · fixed in 6.3.9600.20402
- Microsoft Windows Server 2008 R2 Service Pack 1
From 6.1.7601.0 · fixed in 6.1.7601.25984
- Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)
From 6.1.7601.0 · fixed in 6.1.7601.25984
- Microsoft Windows Server 2012
From 6.2.9200.0 · fixed in 6.2.9200.23736
- Microsoft Windows Server 2012 (Server Core installation)
From 6.2.9200.0 · fixed in 6.2.9200.23736
- Microsoft Windows Server 2012 R2
From 6.3.9600.0 · fixed in 6.3.9600.20402
- Microsoft Windows Server 2012 R2 (Server Core installation)
From 6.3.9600.0 · fixed in 6.3.9600.20402