CVE-2022-34713
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMicrosoft Windows Support Diagnostic Tool (MSDT) Remote Code Execution Vulnerability
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCVE-2022-34713 is a Remote Code Execution vulnerability in the Microsoft Windows Support Diagnostic Tool (MSDT). Attackers can execute arbitrary code by tricking users into opening malicious documents or visiting crafted URLs that invoke MSDT, leveraging the diagnostic tool's URI protocol handler.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 10.0.10240.19387< 10.0.14393.5291< 10.0.17763.3287< 10.0.19042.1889< 10.0.19043.1889< 10.0.19044.1889< 10.0.22000.856all versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Windows version and build numberOpen Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the full Windows version and build number.Affected if The Windows version is one of the affected releases (10 1507, 1607, 1809, 20h2, 21h1, 21h2, or 11 21h2) and the build number is lower than the specified threshold (10.0.10240.19387, 10.0.14393.5291, 10.0.17763.3287, 10.0.19042.1889, 10.0.19043.1889, 10.0.19044.1889, or 10.0.22000.856 respectively),
-
Verify MSDT executable existsCheck for the presence of msdt.exe in the system. Run 'dir /s C:\msdt.exe' or look in default locations such as 'C:\Windows\System32\msdt.exe' and 'C:\Windows\SysWOW64\msdt.exe'.Affected if The msdt.exe file exists on the system, indicating MSDT is installed and available for invocation.
-
Check MSDT URL protocol handler statusOpen Registry Editor and navigate to 'HKEY_CLASSES_ROOT\ms-msdt' or run 'reg query HKEY_CLASSES_ROOT\ms-msdt' from an elevated command prompt to see if the URL protocol handler is registered.Affected if The ms-msdt key exists in the registry, meaning the URL protocol handler is enabled and the vulnerability can be triggered via malicious URLs.
-
Check for diagnostic file associationRun 'reg query HKEY_CLASSES_ROOT\.diagcab' or check if .diagcab files are associated with MSDT to determine if diagnostic package files can trigger the vulnerability.Affected if The .diagcab file extension is associated with MSDT, allowing specially crafted diagnostic files to invoke the vulnerable component.
A system is affected if it runs a Windows version within the affected ranges (including any Windows 7 version) and has MSDT installed with the URL protocol handler or file associations enabled, allowing the memory corruption flaw to be triggered via malicious diagnostic files or URLs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.0.10240.1938710.0.14393.529110.0.17763.3287
Apply the Microsoft security update for this vulnerability and/or disable MSDT URL protocol as an interim workaround; test that Windows diagnostic functionality remains operational after changes.
Windows 10 1507: 10.0.10240.19387+ | Windows 10 1607: 10.0.14393.5291+ | Windows 10 1809: 10.0.17763.3287+ | Windows 10 20h2: 10.0.19042.1889+ | Windows 10 21h1: 10.0.19043.1889+ | Windows 10 21h2: 10.0.19044.1889+ | Windows 11 21h2: 10.0.22000.856+
- Open Settings > Update & Security > Windows Update and check for updates
- Install all available cumulative updates for your Windows version
- Restart the system when prompted
- Verify the installed version matches or exceeds: Windows 10 1507: 10.0.10240.19387 | Windows 10 1607: 10.0.14393.5291 | Windows 10 1809: 10.0.17763.3287 | Windows 10 20h2: 10.0.19042.1889 | Windows 10 21h1: 10.0.19043.1889 | Windows 10 21h2: 10.0.19044.1889 | Windows 11 21h2: 10.0.22000.856
- For Windows 7 (end-of-life): Microsoft has end-of-support; migrate to a supported Windows version such as Windows 10 or 11
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34713 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-34713 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data