CVE-2022-30190
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 · uneditedA 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.
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 confidenceThis is the 'Follina' vulnerability (CVE-2022-30190) - a remote code execution flaw in Microsoft Support Diagnostic Tool (MSDT) triggered via URL protocol when called from applications like Word. Attackers embed malicious code in Office documents that invoke MSDT, achieving code execution with the privileges of the calling application.
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.19325< 10.0.14393.5192< 10.0.17763.3046< 10.0.19042.1766< 10.0.19043.1766< 10.0.19044.1766< 10.0.22000.739all 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 your Windows versionRun 'winver' or 'systeminfo' and note the full version number (for example, 10.0.19044.xxxx)Affected if The version falls within any of these ranges: Windows 10 1507 < 10.0.10240.19325, Windows 10 1607 < 10.0.14393.5192, Windows 10 1809 < 10.0.17763.3046, Windows 10 20h2 < 10.0.19042.1766, Windows 10 21h1 < 10.0.19043.1766, Windows 10 21h2 < 10.0.19044.1766, Windows 11 21h2 < 10.0.22000.739, or Window
-
Locate the MSDT executableSearch for 'msdt.exe' in the Windows\System32 directory or check if the file exists at typical locationsAffected if The MSDT executable exists on the system (its presence is required for the vulnerability to be exploitable)
-
Check if MSDT URL protocol handler is registeredExamine the Windows registry under HKCR\ for an MSDT protocol handler entry (such as 'ms-msdt:' or similar URL scheme entries)Affected if A URL protocol handler for MSDT is registered in the registry, allowing applications to invoke MSDT via URL schemes
-
Verify if the system has Microsoft security updates for this CVECheck Windows Update history or the installed KB list for security updates released after June 2022 that address this vulnerability (such as KB5014697 and subsequent MSDT-related patches)Affected if No relevant security updates from June 2022 or later are installed, meaning the vulnerability remains unpatched
Your environment is affected if you are running any Windows version within the affected ranges listed AND the MSDT URL protocol handler is registered, and no corresponding security updates have been installed.
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.1932510.0.14393.519210.0.17763.3046
Disable the MSDT URL protocol handler via registry modification (set HKCR\ms-msdt\Enabled = 0) or apply Microsoft patches; also enable Protected View in Office to block documents from executing external content.
Apply May 2022 Patch Tuesday updates (or later) to reach the fixed build versions: 10.0.10240.19325 (1507), 10.0.14393.5192 (1607), 10.0.17763.3046 (1809), 10.0.19042.1766 (20h2), 10.0.19043.1766 (21h1), 10.0.19044.1766 (21h2), 10.0.22000.739 (11 21h2)
- Apply the May 2022 Windows security updates (CVE-2022-30190) from Microsoft Update or your organization's patch management system.
- For Windows 10 1507, update to version 10.0.10240.19325 or later.
- For Windows 10 1607, update to version 10.0.14393.5192 or later.
- For Windows 10 1809, update to version 10.0.17763.3046 or later.
- For Windows 10 20h2, update to version 10.0.19042.1766 or later.
- For Windows 10 21h1, update to version 10.0.19043.1766 or later.
- For Windows 10 21h2, update to version 10.0.19044.1766 or later.
- For Windows 11 21h2, update to version 10.0.22000.739 or later.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30190 — 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-30190 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