CVE-2022-30190 remediation guide

Microsoft Windows 10 Version 1809, Windows Server 2019, Windows Server 2019 (Server Core installation)

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.

Open CVE record

ProductMicrosoft Windows 10 Version 1809, Windows Server 2019, Windows Server 2019 (Server Core installation)

Affected versions>= 10.0.17763.0 < 10.0.17763.3046, >= 10.0.0 < 10.0.17763.3046, >= 10.0.0 < 10.0.19043.1766, >= 10.0.20348.0 < 10.0.20348.770, >= 10.0.0 < 10.0.19042.1766, >= 10.0.0 < 10.0.22000.739, >= 10.0.19043.0 < 10.0.19044.1766, >= 10.0.10240.0 < 10.0.10240.19325, >= 10.0.14393.0 < 10.0.14393.5192, >= 6.1.0 < 6.1.7601.25984, >= 6.3.0 < 6.3.9600.20402, >= 6.1.7601.0 < 6.1.7601.25984, >= 6.2.9200.0 < 6.2.9200.23736, >= 6.3.9600.0 < 6.3.9600.20402, < 10.0.10240.19325, < 10.0.14393.5192, < 10.0.17763.3046, < 10.0.19042.1766, < 10.0.19043.1766, < 10.0.19044.1766

Fixed versions10.0.10240.19325, 10.0.14393.5192, 10.0.17763.3046, 10.0.19042.1766, 10.0.19043.1766, 10.0.19044.1766, 10.0.22000.739, 10.0.20348.770

Priority basisImmediate · CVSS 7.8 · EPSS 99.4%

Identify the affected asset

Confirm whether Microsoft Windows 10 Version 1809, Windows Server 2019, Windows Server 2019 (Server Core installation) is installed, record the deployed version and installation path, and identify exposed interfaces.

Record the product name, package or appliance identifier, and installed version.
Identify internet-facing, administrative, API, and internal access paths.
Preserve the pre-change configuration and relevant service logs.

Validate the affected-version match

Compare the deployed version with the affected range: >= 10.0.17763.0 < 10.0.17763.3046, >= 10.0.0 < 10.0.17763.3046, >= 10.0.0 < 10.0.19043.1766, >= 10.0.20348.0 < 10.0.20348.770, >= 10.0.0 < 10.0.19042.1766, >= 10.0.0 < 10.0.22000.739, >= 10.0.19043.0 < 10.0.19044.1766, >= 10.0.10240.0 < 10.0.10240.19325, >= 10.0.14393.0 < 10.0.14393.5192, >= 6.1.0 < 6.1.7601.25984, >= 6.3.0 < 6.3.9600.20402, >= 6.1.7601.0 < 6.1.7601.25984, >= 6.2.9200.0 < 6.2.9200.23736, >= 6.3.9600.0 < 6.3.9600.20402, < 10.0.10240.19325, < 10.0.14393.5192, < 10.0.17763.3046, < 10.0.19042.1766, < 10.0.19043.1766, < 10.0.19044.1766. Treat incomplete inventory results as unresolved.

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

Apply supported remediation

Apply updates per vendor instructions.

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

Confirm the expected version and package state.
Run a functional health check for critical service paths.
Review authentication, error, application, and security monitoring logs.
Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.