CVSS 3.1
7.8 highCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HKnown 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.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExplain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Microsoft Windows 10 Version 1809 | from 10.0.17763.0 before 10.0.17763.3046 |
| Microsoft Windows 10 Version 1809 | from 10.0.0 before 10.0.17763.3046 |
| Microsoft Windows Server 2019 | from 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 21H1 | from 10.0.0 before 10.0.19043.1766 |
| Microsoft Windows Server 2022 | from 10.0.20348.0 before 10.0.20348.770 |
| Microsoft Windows 10 Version 20H2 | from 10.0.0 before 10.0.19042.1766 |
| Microsoft Windows Server version 20H2 | from 10.0.0 before 10.0.19042.1766 |
| Microsoft Windows 11 version 21H2 | from 10.0.0 before 10.0.22000.739 |
| Microsoft Windows 10 Version 21H2 | from 10.0.19043.0 before 10.0.19044.1766 |
| Microsoft Windows 10 Version 1507 | from 10.0.10240.0 before 10.0.10240.19325 |
| Microsoft Windows 10 Version 1607 | from 10.0.14393.0 before 10.0.14393.5192 |
| Microsoft Windows Server 2016 | from 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 7 | from 6.1.0 before 6.1.7601.25984 |
| Microsoft Windows 7 Service Pack 1 | from 6.1.0 before 6.1.7601.25984 |
| Microsoft Windows 8.1 | from 6.3.0 before 6.3.9600.20402 |
| Microsoft Windows Server 2008 R2 Service Pack 1 | from 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 2012 | from 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 R2 | from 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 |
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.
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.