CVE-2022-34713: Microsoft Windows Support Diagnostic Tool (MSDT) Remote Code Execution
Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2022-08-09.
- CVSS v3.1 (CVE record)
- 7.8
- high
- EPSS (exploit probability, 30 days)
- 68%
- higher than 99.3% of all CVEs
- Added to CISA KEV
- 2022-08-09
- US federal due date 2022-08-30
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2022-34713 explained
CVE-2022-34713 is a remote code execution vulnerability in the Microsoft Windows Support Diagnostic Tool (MSDT). It exists when MSDT is called using the URL protocol from a calling application. CISA lists it as known to be exploited by attackers, so affected Windows client and server systems should be updated promptly.
Impact
Successful exploitation can lead to code execution with high impact on confidentiality, integrity and availability of the affected system. The attack vector is local, complexity is low, no privileges are required, but user interaction is needed. CISA rates the technical impact as total and automatable as no. Attackers are known to use this vulnerability; whether it is used in ransomware campaigns is unknown.
Who is affected
The CVE record lists Windows 10 Version 1809, Windows Server 2019 and its Server Core installation (fixed in 10.0.17763.3287), Windows 10 Version 21H1 (10.0.19043.1889), 20H2 and Windows Server version 20H2 (10.0.19042.1889), 21H2 (10.0.19044.1889), Windows 11 version 21H2 (10.0.22000.856), Windows Server 2022 (10.0.20348.887), Windows 10 Version 1507 (10.0.10240.19387), and Windows 10 Version 1607 and Windows Server 2016 (10.0.14393.5291). Earlier builds are affected. Further products are listed on the page.
Written with AI from the data on this page and checked against it automatically.
Official description
A remote code execution vulnerability exists when Microsoft Windows MSDT is called using the URL protocol from a calling application.
CISA required action: Apply updates per vendor instructions.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Microsoft Windows 10 Version 180932-bit, x64, ARM64AffectedFixed in
- < 10.0.17763.3287
- 10.0.17763.3287
- Microsoft Windows Server 2019x64AffectedFixed in
- < 10.0.17763.3287
- 10.0.17763.3287
- Microsoft Windows Server 2019 (Server Core installation)x64AffectedFixed in
- < 10.0.17763.3287
- 10.0.17763.3287
- Microsoft Windows 10 Version 21H1x64, ARM64, 32-bitAffectedFixed in
- < 10.0.19043.1889
- 10.0.19043.1889
- Microsoft Windows Server 2022x64AffectedFixed in
- < 10.0.20348.887
- 10.0.20348.887
- Microsoft Windows 10 Version 20H232-bit, ARM64AffectedFixed in
- < 10.0.19042.1889
- 10.0.19042.1889
- Microsoft Windows Server version 20H2x64AffectedFixed in
- < 10.0.19042.1889
- 10.0.19042.1889
- Microsoft Windows 11 version 21H2x64, ARM64AffectedFixed in
- < 10.0.22000.856
- 10.0.22000.856
- Microsoft Windows 10 Version 21H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19044.1889
- 10.0.19044.1889
- Microsoft Windows 10 Version 150732-bit, x64AffectedFixed in
- < 10.0.10240.19387
- 10.0.10240.19387
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 10 Version 180932-bit, x64, ARM64 |
|
|
| Microsoft Windows Server 2019x64 |
|
|
| Microsoft Windows Server 2019 (Server Core installation)x64 |
|
|
| Microsoft Windows 10 Version 21H1x64, ARM64, 32-bit |
|
|
| Microsoft Windows Server 2022x64 |
|
|
| Microsoft Windows 10 Version 20H232-bit, ARM64 |
|
|
| Microsoft Windows Server version 20H2x64 |
|
|
| Microsoft Windows 11 version 21H2x64, ARM64 |
|
|
| Microsoft Windows 10 Version 21H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 10 Version 150732-bit, x64 |
|
|
Show 12 more products
- Microsoft Windows 10 Version 160732-bit, x64AffectedFixed in
- < 10.0.14393.5291
- 10.0.14393.5291
- Microsoft Windows Server 2016x64AffectedFixed in
- < 10.0.14393.5291
- 10.0.14393.5291
- Microsoft Windows Server 2016 (Server Core installation)x64AffectedFixed in
- < 10.0.14393.5291
- 10.0.14393.5291
- Microsoft Windows 732-bitAffectedFixed in
- < 6.1.7601.26065
- 6.1.7601.26065
- Microsoft Windows 7 Service Pack 1x64AffectedFixed in
- < 6.1.7601.26065
- 6.1.7601.26065
- Microsoft Windows 8.132-bit, x64, ARM64AffectedFixed in
- < 6.3.9600.20520
- 6.3.9600.20520
- Microsoft Windows Server 2008 R2 Service Pack 1x64AffectedFixed in
- < 6.1.7601.26065
- 6.1.7601.26065
- Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64AffectedFixed in
- < 6.1.7601.26065
- 6.1.7601.26065
- Microsoft Windows Server 2012x64AffectedFixed in
- < 6.2.9200.23817
- 6.2.9200.23817
- Microsoft Windows Server 2012 (Server Core installation)x64AffectedFixed in
- < 6.2.9200.23817
- 6.2.9200.23817
- Microsoft Windows Server 2012 R2x64AffectedFixed in
- < 6.3.9600.20520
- 6.3.9600.20520
- Microsoft Windows Server 2012 R2 (Server Core installation)x64AffectedFixed in
- < 6.3.9600.20520
- 6.3.9600.20520
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 10 Version 160732-bit, x64 |
|
|
| Microsoft Windows Server 2016x64 |
|
|
| Microsoft Windows Server 2016 (Server Core installation)x64 |
|
|
| Microsoft Windows 732-bit |
|
|
| Microsoft Windows 7 Service Pack 1x64 |
|
|
| Microsoft Windows 8.132-bit, x64, ARM64 |
|
|
| Microsoft Windows Server 2008 R2 Service Pack 1x64 |
|
|
| Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)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 |
|
|
How to fix it
- Update to the fixed version for your product:
- Microsoft Windows 10 Version 1809: 10.0.17763.3287
- Microsoft Windows Server 2019: 10.0.17763.3287
- Microsoft Windows Server 2019 (Server Core installation): 10.0.17763.3287
- Microsoft Windows 10 Version 21H1: 10.0.19043.1889
- Microsoft Windows Server 2022: 10.0.20348.887
- Microsoft Windows 10 Version 20H2: 10.0.19042.1889
- Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2022-34713
- CISA's deadline for US federal agencies: 2022-08-30 (passed) – a useful benchmark for everyone else, too.
What to do
- Install the Microsoft security update that brings each system to the fixed build listed for its Windows version or later.
- Prioritize systems where users open documents, links or content from external sources.
- Follow the Microsoft advisory for any additional guidance or mitigations.
- Verify build numbers across the fleet to confirm the updates were applied.
- Check systems for signs of compromise, since attackers are known to use this vulnerability.
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
Questions about CVE-2022-34713
- Is CVE-2022-34713 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-08-09 with a US federal due date of 2022-08-30. Whether it is used in ransomware campaigns is unknown.
- Does exploitation require user action?
- Yes. The CVSS vector states that user interaction is required and no privileges are needed. The attack vector is rated local.
- What does CISA require?
- CISA's required action is to apply updates per vendor instructions. Install the Microsoft update that raises each system to the fixed build listed for its Windows version.
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.