CriticalCVE-2022-34713

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

Published 09.08.2022In CISA KEV since 09.08.2022Sources: SingCERT, CVE.org

Actively exploited
Source: CSA/SingCERT How we classify

What is affected, what to do

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

The vulnerability is being actively exploited; treat it as a priority. Update Microsoft Windows 10 Version 1809 to version 10.0.17763.3287, Microsoft Windows Server 2019 to version 10.0.17763.3287, Microsoft Windows Server 2019 (Server Core installation) to version 10.0.17763.3287. Immediate actions, mitigation and detection rules are in the runbook below.

Affected: Microsoft Windows 10 Version 1809 lt 10.0.17763.0..10.0.17763.3287
Microsoft Windows Server 2019 lt 10.0.17763.0..10.0.17763.3287
Microsoft Windows Server 2019 (Server Core installation) lt 10.0.17763.0..10.0.17763.3287
Microsoft Windows 10 Version 21H1 lt 10.0.0..10.0.19043.1889
Microsoft Windows Server 2022 lt 10.0.20348.0..10.0.20348.887
Microsoft Windows 10 Version 20H2 lt 10.0.0..10.0.19042.1889
Microsoft Windows Server version 20H2 lt 10.0.0..10.0.19042.1889
Microsoft Windows 11 version 21H2 lt 10.0.0..10.0.22000.856
Microsoft Windows 10 Version 21H2 lt 10.0.19043.0..10.0.19044.1889
Microsoft Windows 10 Version 1507 lt 10.0.10240.0..10.0.10240.19387
Microsoft Windows 10 Version 1607 lt 10.0.14393.0..10.0.14393.5291
Microsoft Windows Server 2016 lt 10.0.14393.0..10.0.14393.5291
Microsoft Windows Server 2016 (Server Core installation) lt 10.0.14393.0..10.0.14393.5291
Microsoft Windows 7 lt 6.1.0..6.1.7601.26065
Microsoft Windows 7 Service Pack 1 lt 6.1.0..6.1.7601.26065
Microsoft Windows 8.1 lt 6.3.0..6.3.9600.20520
Microsoft Windows Server 2008 R2 Service Pack 1 lt 6.1.7601.0..6.1.7601.26065
Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation) lt 6.1.7601.0..6.1.7601.26065
Microsoft Windows Server 2012 lt 6.2.9200.0..6.2.9200.23817
Microsoft Windows Server 2012 (Server Core installation) lt 6.2.9200.0..6.2.9200.23817
Microsoft Windows Server 2012 R2 lt 6.3.9600.0..6.3.9600.20520
Microsoft Windows Server 2012 R2 (Server Core installation) lt 6.3.9600.0..6.3.9600.20520
Fixed in: 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
Microsoft Windows Server version 20H2 10.0.19042.1889
Microsoft Windows 11 version 21H2 10.0.22000.856
Microsoft Windows 10 Version 21H2 10.0.19044.1889
Microsoft Windows 10 Version 1507 10.0.10240.19387
Microsoft Windows 10 Version 1607 10.0.14393.5291
Microsoft Windows Server 2016 10.0.14393.5291
Microsoft Windows Server 2016 (Server Core installation) 10.0.14393.5291
Microsoft Windows 7 6.1.7601.26065
Microsoft Windows 7 Service Pack 1 6.1.7601.26065
Microsoft Windows 8.1 6.3.9600.20520
Microsoft Windows Server 2008 R2 Service Pack 1 6.1.7601.26065
Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation) 6.1.7601.26065
Microsoft Windows Server 2012 6.2.9200.23817
Microsoft Windows Server 2012 (Server Core installation) 6.2.9200.23817
Microsoft Windows Server 2012 R2 6.3.9600.20520
Microsoft Windows Server 2012 R2 (Server Core installation) 6.3.9600.20520

Not sure whether and how you are affected? Ask a question about this vulnerability

Metrics

7.8

Priority

XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

Source: NVD, CVSS v3

7.8

CVSS v3

Severity High on the scale from 0 to 10.

Source: SingCERT, CVE.org

67.8 %

EPSS score

High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

Source: FIRST EPSS, percentile 99.31

Show all metrics

Severity: Critical
Priority (0–325) The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first? Read in glossary: 219.14 Methodology
Exploit maturity An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack. Read in glossary: actively exploitedSource: CSA/SingCERT How we classify
XIEM Effective CVSS XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command. Read in glossary: 7.8 Methodology
CVSS v3 CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions. Read in glossary: 7.8
EPSS score The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“. Read in glossary: 67.8 %; High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
EPSS percentile The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking. Read in glossary: 99.31; Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
KEV status The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching. Read in glossary: Actively exploited
Published: 09.08.2022
In CISA KEV since The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching. Read in glossary: 09.08.2022

Response and mitigation

Why act now?

Prioritisation rationale

This flaw, publicly known as "DogWalk", lets a crafted diagnostic package abuse a path traversal so that MSDT drops an arbitrary file into the user's Startup folder, with code execution following at the next logon. The vector is local, requires user interaction but no privileges, and fits phishing campaigns that sidestep Office macro blocking. Exploitation likelihood is very high, though CISA records no known ransomware use. Organisations with large client fleets, residual Windows 7 estates or patchy update hygiene should treat this as high priority and close it within the normal patch cycle, no later than 14 days. Fully patched clients with the ASR rule enforced carry substantially reduced residual risk.

01
Runbook step 1
Immediate response (0-24 h)
- Deploy the August 2022 cumulative security update. Minimum builds per the vendor data: Windows 10 1507 → 10.0.10240.19387, 1607 → 10.0.14393.5291, 1809 → 10.0.17763.3287, 20H2 → 10.0.19042.1889, 21H1 → 10.0.19043.1889, 21H2 → 10.0.19044.1889, Windows 11 21H2 → 10.0.22000.856, Windows 7 → 6.1.7601.26065 (ESU only). Look up the KB IDs per build in the Microsoft Security Update Guide. Server editions are not listed in this context, so verify their exposure in the vendor advisory.
- Measure patch compliance. Use Intune, SCCM/MECM, or the build number plus UBR from HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion to list every client below these builds. Treat unpatched Windows 7 hosts without ESU as unremediable and isolate them.
- Cut the delivery channel. Block .diagcab, .diagpkg and .diagcfg at the mail gateway and web proxy, including inside ZIP and ISO containers. Purge already-delivered messages carrying these attachments.
- Disable the ms-msdt URL protocol on hosts that cannot be patched today. Back up the key first with reg export HKCR\ms-msdt msdt.reg, then remove it with reg delete HKCR\ms-msdt /f. Roll this out via GPO or an Intune script.
- Sweep Startup folders. Check %APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup and C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp for files created during the exposure window.
02
Runbook step 2
Mitigation layers
- Configuration (GPO): Disable scripted diagnostics by setting EnableDiagnostics=0 (DWORD) under HKLM\SOFTWARE\Policies\Microsoft\Windows\ScriptedDiagnostics. In the policy editor this is under "Administrative Templates › System › Troubleshooting and Diagnostics › Scripted Diagnostics". Also turn off online troubleshooting content.
- Endpoint hardening (ASR): Enforce "Block all Office applications from creating child processes" (d4f940ab-401b-4efc-aadc-ad5f3c50688a) in block mode. Add "Block executable content from email client and webmail" alongside it.
- Application control: Use AppLocker or WDAC to deny msdt.exe to standard users and allow it only for helpdesk groups. Remap the .diagcab file association via GPO to a benign handler.
- Mark-of-the-Web: Ensure ISO, VHD and ZIP handling propagates MotW to extracted files. Keep Windows builds current and configure third-party archivers to propagate MotW.
- IAM / least privilege: Keep end users off local admin. Exploitation runs in user context, so removing admin rights limits persistence to the user profile.
- Network: Block outbound SMB (TCP 445) and WebDAV from client VLANs to the internet. This prevents diagnostic packages from being pulled from attacker-controlled shares.
03
Runbook step 3
Detection rules
- Process ancestry (Sysmon EID 1 / Security 4688): Flag msdt.exe spawned by Office, Outlook, browsers or explorer.exe with .diagcab or ms-msdt: on the command line. KQL: DeviceProcessEvents | where FileName =~ "msdt.exe" and (ProcessCommandLine has_any (".diagcab","ms-msdt:") or InitiatingProcessFileName in~ ("winword.exe","outlook.exe","msedge.exe","chrome.exe"))
- Startup-folder writes (Sysmon EID 11): msdt.exe or sdiagnhost.exe writing a file into \Start Menu\Programs\Startup\ is the core path-traversal indicator. KQL: DeviceFileEvents | where InitiatingProcessFileName in~ ("msdt.exe","sdiagnhost.exe") and FolderPath has @"\Start Menu\Programs\Startup"
- Children of sdiagnhost.exe: Treat cmd.exe, powershell.exe, rundll32.exe or mshta.exe under sdiagnhost.exe as high severity. Sigma shape: ParentImage|endswith: '\sdiagnhost.exe' combined with Image|endswith on LOLBins.
- Download telemetry: Search the proxy log or Zeek http.log for .diagcab URIs or application/vnd.ms-cab-compressed MIME types. Also check Sysmon EID 15 for a Zone.Identifier stream on *.diagcab files.
- Mail gateway logs: Hunt back 90 days for inbound .diagcab attachments and correlate with endpoint hits.

Detection rules

No NEOSEC detection rule is available for this vulnerability yet.

Classification under NIS2 and CRA

Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

NIS2 NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management. Read in glossary: Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
CRA The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates. Read in glossary: Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
ISO/IEC 27001 ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security. Read in glossary: Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

Description

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

Source: CSA/SingCERT, NVD (NIST), cvelistv5, CISA KEV Catalog, CVE.org (MITRE)

Affected products

The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

Affected products
		Affected versions	Fixed in
Microsoft	Windows 10 Version 1507	`10.0.10240.0 – < 10.0.10240.19387`	`10.0.10240.19387`
Microsoft	Windows 10 Version 1607	`10.0.14393.0 – < 10.0.14393.5291`	`10.0.14393.5291`
Microsoft	Windows 10 Version 1809	`10.0.17763.0 – < 10.0.17763.3287`	`10.0.17763.3287`
Microsoft	Windows 10 Version 20H2	`10.0.0 – < 10.0.19042.1889`	`10.0.19042.1889`
Microsoft	Windows 10 Version 21H1	`10.0.0 – < 10.0.19043.1889`	`10.0.19043.1889`
Microsoft	Windows 10 Version 21H2	`10.0.19043.0 – < 10.0.19044.1889`	`10.0.19044.1889`
Microsoft	Windows 11 version 21H2	`10.0.0 – < 10.0.22000.856`	`10.0.22000.856`
Microsoft	Windows 7	`6.1.0 – < 6.1.7601.26065`	`6.1.7601.26065`
Microsoft	Windows 7 Service Pack 1	`6.1.0 – < 6.1.7601.26065`	`6.1.7601.26065`
Microsoft	Windows 8.1	`6.3.0 – < 6.3.9600.20520`	`6.3.9600.20520`
Microsoft	Windows Server 2008 R2 Service Pack 1	`6.1.7601.0 – < 6.1.7601.26065`	`6.1.7601.26065`
Microsoft	Windows Server 2008 R2 Service Pack 1 (Server Core installation)	`6.1.7601.0 – < 6.1.7601.26065`	`6.1.7601.26065`
Microsoft	Windows Server 2012	`6.2.9200.0 – < 6.2.9200.23817`	`6.2.9200.23817`
Microsoft	Windows Server 2012 (Server Core installation)	`6.2.9200.0 – < 6.2.9200.23817`	`6.2.9200.23817`
Microsoft	Windows Server 2012 R2	`6.3.9600.0 – < 6.3.9600.20520`	`6.3.9600.20520`
Microsoft	Windows Server 2012 R2 (Server Core installation)	`6.3.9600.0 – < 6.3.9600.20520`	`6.3.9600.20520`
Microsoft	Windows Server 2016	`10.0.14393.0 – < 10.0.14393.5291`	`10.0.14393.5291`
Microsoft	Windows Server 2016 (Server Core installation)	`10.0.14393.0 – < 10.0.14393.5291`	`10.0.14393.5291`
Microsoft	Windows Server 2019	`10.0.17763.0 – < 10.0.17763.3287`	`10.0.17763.3287`
Microsoft	Windows Server 2019 (Server Core installation)	`10.0.17763.0 – < 10.0.17763.3287`	`10.0.17763.3287`
Microsoft	Windows Server 2022	`10.0.20348.0 – < 10.0.20348.887`	`10.0.20348.887`
Microsoft	Windows Server version 20H2	`10.0.0 – < 10.0.19042.1889`	`10.0.19042.1889`

Vendors and products

Affected operating systems

Affected operating systems

Windows	microsoft	windows_10_1507	—
Windows	microsoft	windows_10_1607	—
Windows	microsoft	windows_10_1809	—
Windows	microsoft	windows_10_20h2	—
Windows	microsoft	windows_10_21h1	—
Windows	microsoft	windows_10_21h2	—
Windows	microsoft	windows_11_21h2	—
Windows	microsoft	windows_7	—
Windows	microsoft	windows_8.1	—
Windows	microsoft	windows_rt_8.1	—
Windows	microsoft	windows_server_2008	`r2`
Windows	microsoft	windows_server_2012	`r2`
Windows	microsoft	windows_server_2012	—
Windows	microsoft	windows_server_2016	—
Windows	microsoft	windows_server_2019	—
Windows	microsoft	windows_server_2022	—
Windows	microsoft	windows_server_20h2	—

Public exploit references

Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

Public exploit references

CISA KEV Catalog	CISA Known Exploited Vulnerability (opens in a new tab)cisa.gov	actively exploited	09.08.2022
CSA/SingCERT	Active Exploitation of Microsoft Windows Support Diagnostic Tool (MSDT) (opens in a new tab)CSA/SingCERT	actively exploited	09.08.2022

References & sources

Microsoft Security Update GuideMicrosoft Windows Support Diagnostic Tool (MSDT) Remote Code Execution VulnerabilityVendor advisory, Patch, Vendor advisory
cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2022-34713government-resource, US government resource

Embed badge

Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

<a href="https://intel.neosec.eu/en/cve/CVE-2022-34713"><img src="https://intel.neosec.eu/badge/cve/CVE-2022-34713.svg?lang=en" alt="CVE-2022-34713 – NEOSEC Intel" height="20"></a>

What is affected, what to do

Metrics

Response and mitigation

Prioritisation rationale

Immediate response (0-24 h)

Mitigation layers

Detection rules

Detection rules

Classification under NIS2 and CRA

Description

Affected products

Vendors and products

Affected operating systems

Public exploit references

References & sources