CVE-2022-34713: Microsoft Windows Support Diagnostic Tool (MSDT) Remote Code Execution Vulnerability

Published Aug 9, 2022
·
Updated

A remote code execution vulnerability exists when Microsoft Windows MSDT is called using the URL protocol from a calling application.

Other sources

Microsoft Windows Support Diagnostic Tool (MSDT) Remote Code Execution Vulnerability

Microsoft

Affected Software

78 affected componentsFixes available
Microsoft Windows 10=20H2
Microsoft Windows 10
Microsoft Windows 10
Microsoft Windows 10=20h2
Microsoft Windows 10=20h2
Microsoft Windows 10=20h2
Microsoft Windows 10=21h1
Microsoft Windows 10=21h1
Microsoft Windows 10=21h1
Microsoft Windows 10=21h2
Microsoft Windows 10=21h2
Microsoft Windows 10=21h2
Microsoft Windows 10=1607
Microsoft Windows 10=1607
Microsoft Windows 10=1809
Microsoft Windows 10=1809
Microsoft Windows 10=1809
Microsoft Windows 11
Microsoft Windows 11
Microsoft Windows 7=sp1
Microsoft Windows 7=sp1
Microsoft Windows 8.1
Microsoft Windows 8.1
Microsoft Windows RT 8.1
Microsoft Windows Server 2008=r2-sp1
Microsoft Windows Server 2012
Microsoft Windows Server 2012=r2
Microsoft Windows Server 2016
Microsoft Windows Server 2016=20h2
Microsoft Windows Server 2019
Microsoft Windows Server 2022
Microsoft Windows
Microsoft Windows 10 1507<10.0.10240.19387
Microsoft Windows 10 1607<10.0.14393.5291
Microsoft Windows 10 1809<10.0.17763.3287
Microsoft Windows 10 20h2<10.0.19042.1889
Microsoft Windows 10 21h1<10.0.19043.1889
Microsoft Windows 10 21h2<10.0.19044.1889
Microsoft Windows 11 21h2<10.0.22000.856
Microsoft Windows Server 2016<10.0.14393.5291
Microsoft Windows Server 2019<10.0.17763.3287
Microsoft Windows Server 2022<10.0.20348.887
Microsoft Windows Server 20h2<10.0.19042.1889
Microsoft Windows Server 2012 R2<6.3.9600.20520
6.3.9600.20520
Microsoft Windows Server 2012 R2<6.3.9600.20520
6.3.9600.20520
Microsoft Windows Server 2012<6.2.9200.23817
6.2.9200.23817
Microsoft Windows Server 2008 R2<6.1.7601.26065
6.1.7601.26065
Microsoft Windows 8.1 for x64-based systems<6.3.9600.20520
6.3.9600.20520
Microsoft Windows Server 2012<6.2.9200.23817
6.2.9200.23817
Microsoft Windows Server 2008 R2<6.1.7601.26065
6.1.7601.26065
Microsoft Windows 7<6.1.7601.26065
6.1.7601.26065
Microsoft Windows 7<6.1.7601.26065
6.1.7601.26065
Microsoft Windows RT 8.1<6.3.9600.20520
6.3.9600.20520
Microsoft Windows 8.1 for 32-bit systems<6.3.9600.20520
6.3.9600.20520
Microsoft Windows Server 2016<10.0.14393.5291
10.0.14393.5291
Microsoft Windows 10<10.0.10240.19387
10.0.10240.19387
Microsoft Windows 10=1607
10.0.14393.5291
Microsoft Windows 10<10.0.10240.19387
10.0.10240.19387
Microsoft Windows 10=21H2
10.0.19044.1889
Microsoft Windows Server 2016<10.0.14393.5291
10.0.14393.5291
Microsoft Windows 10=21H2
10.0.19044.1889
Microsoft Windows 10=1607
10.0.14393.5291
Microsoft Windows 10=21H2
10.0.19044.1889
Microsoft Windows 11=21H2
10.0.22000.856
Microsoft Windows Server=20H2
10.0.19042.1889
Microsoft Windows 11=21H2
10.0.22000.856
Microsoft Windows 10=21H1
10.0.19043.1889
Microsoft Windows 10=20H2
10.0.19042.1889
Microsoft Windows Server 2022<10.0.20348.887
10.0.20348.887
Microsoft Windows Server 2022<10.0.20348.887
10.0.20348.887
Microsoft Windows 10=20H2
10.0.19042.1889
Microsoft Windows 10=21H1
10.0.19043.1889
Microsoft Windows Server 2019<10.0.17763.3287
10.0.17763.3287
Microsoft Windows Server 2019<10.0.17763.3287
10.0.17763.3287
Microsoft Windows 10=21H1
10.0.19043.1889
Microsoft Windows 10=1809
10.0.17763.3287
Microsoft Windows 10=1809
10.0.17763.3287
Microsoft Windows 10=1809
10.0.17763.3287

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 6.3.9600.20520Patch KB5016683
  2. Upgrade

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

    Fixed in 6.1.7601.26065Patch KB5016679
  3. Upgrade

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

    Fixed in 6.2.9200.23817Patch KB5016684
  4. Upgrade

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

    Fixed in 6.3.9600.20520Patch KB5016681
  5. Upgrade

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

    Fixed in 10.0.14393.5291Patch KB5016622
  6. Upgrade

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

    Fixed in 10.0.10240.19387Patch KB5016639
  7. Upgrade

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

    Fixed in 10.0.19044.1889Patch KB5016616
  8. Upgrade

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

    Fixed in 10.0.22000.856Patch KB5016629
  9. Upgrade

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

    Fixed in 10.0.19042.1889Patch KB5016616
  10. Upgrade

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

    Fixed in 10.0.19043.1889Patch KB5016616
  11. Upgrade

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

    Fixed in 10.0.20348.887Patch KB5016627
  12. Upgrade

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

    Fixed in 10.0.17763.3287Patch KB5016623

Event History

Aug 9, 2022
CVE Published
via CISA·12:00 AM
Known Exploited
via CISA·12: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·07:55 PM
Data Sourced
via MITRE·07:55 PM
DescriptionSeverity
Data Sourced
via NVD·08:15 PM
RemedyDescriptionSeverityAffected Software
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-2022-34713?

CVE-2022-34713 has a critical severity rating, indicating a significant risk for remote code execution.

2

How do I fix CVE-2022-34713?

To mitigate the risk of CVE-2022-34713, install the recommended security patches provided by Microsoft for the affected Windows versions.

3

Which versions of Windows are affected by CVE-2022-34713?

CVE-2022-34713 affects multiple Windows versions, including Windows 10, Windows 11, and various Windows Server editions.

4

What type of vulnerability is CVE-2022-34713?

CVE-2022-34713 is classified as a remote code execution vulnerability impacting the Microsoft Windows Support Diagnostic Tool.

5

Can exploiting CVE-2022-34713 compromise my system?

Yes, successful exploitation of CVE-2022-34713 could allow attackers to run arbitrary code on the affected system, potentially leading to a full compromise.

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