cve.bz

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

7.8 highKEVExploitEPSS 98%Fix available

Known as Follina

High (7.8) in Microsoft Windows. In CISA KEV since 2022-06-14, with known ransomware use. EPSS 98% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
98% (unchanged from 98% a week ago; 99.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2022-06-14, due 2022-07-05, known ransomware use
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2022-05-31. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-30190 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-30190?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-30190?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-30190 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Windows 10 Version 1809from 10.0.17763.0 before 10.0.17763.3046
Microsoft Windows 10 Version 1809from 10.0.0 before 10.0.17763.3046
Microsoft Windows Server 2019from 10.0.17763.0 before 10.0.17763.3046
Microsoft Windows Server 2019 (Server Core installation)from 10.0.17763.0 before 10.0.17763.3046
Microsoft Windows 10 Version 21H1from 10.0.0 before 10.0.19043.1766
Microsoft Windows Server 2022from 10.0.20348.0 before 10.0.20348.770
Microsoft Windows 10 Version 20H2from 10.0.0 before 10.0.19042.1766
Microsoft Windows Server version 20H2from 10.0.0 before 10.0.19042.1766
Microsoft Windows 11 version 21H2from 10.0.0 before 10.0.22000.739
Microsoft Windows 10 Version 21H2from 10.0.19043.0 before 10.0.19044.1766
Microsoft Windows 10 Version 1507from 10.0.10240.0 before 10.0.10240.19325
Microsoft Windows 10 Version 1607from 10.0.14393.0 before 10.0.14393.5192
Microsoft Windows Server 2016from 10.0.14393.0 before 10.0.14393.5192
Microsoft Windows Server 2016 (Server Core installation)from 10.0.14393.0 before 10.0.14393.5192
Microsoft Windows 7from 6.1.0 before 6.1.7601.25984
Microsoft Windows 7 Service Pack 1from 6.1.0 before 6.1.7601.25984
Microsoft Windows 8.1from 6.3.0 before 6.3.9600.20402
Microsoft Windows Server 2008 R2 Service Pack 1from 6.1.7601.0 before 6.1.7601.25984
Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)from 6.1.7601.0 before 6.1.7601.25984
Microsoft Windows Server 2012from 6.2.9200.0 before 6.2.9200.23736
Microsoft Windows Server 2012 (Server Core installation)from 6.2.9200.0 before 6.2.9200.23736
Microsoft Windows Server 2012 R2from 6.3.9600.0 before 6.3.9600.20402
Microsoft Windows Server 2012 R2 (Server Core installation)from 6.3.9600.0 before 6.3.9600.20402

Public exploits

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

2 more

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

  • Emerging Threats Open ET HUNTING Microsoft Windows Support Diagnostic Tool (MSDT) Remote Code Execution 0-click RTF (CVE-2022-30190) sid 2059679
  • Emerging Threats Open ET MALWARE Possible Follina Payload Delivery Page sid 2037082
  • Emerging Threats Open ET EXPLOIT Possible Microsoft Support Diagnostic Tool Exploitation Inbound (CVE-2022-30190) sid 2037083
  • Emerging Threats Open ET EXPLOIT Possible Microsoft Support Diagnostic Tool Exploitation Inbound (CVE-2022-30190) sid 2036726

References

Check your stackJSON