Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Follina, CVE-2022-30190, let a Word document run commands through the Microsoft Support Diagnostic Tool without macros — and even from the Explorer preview pane.

What Is Follina?
Follina is CVE-2022-30190, a remote code execution vulnerability in the Microsoft Support Diagnostic Tool that was abused through Microsoft Office documents. Opening a crafted document ran commands as the current user, with no payload written to disk — a textbook fileless attack. No macros were required, no security warning was shown, and with an RTF variant the Windows Explorer preview pane was enough — the file never had to be opened at all.
The name comes from Kevin Beaumont, who analysed the sample on 27 May 2022 and noticed the number 0438 embedded in it, which is the telephone dialling code for Follina in northern Italy.
Office documents can reference external objects. The malicious document contained a reference to an HTML file on a remote server; that HTML contained a long comment followed by a URL using the ms-msdt: protocol handler.
The MSDT handler accepts parameters, among them IT_BrowseForFile, and the handling of those parameters allowed PowerShell to be invoked through a crafted value. The payload was typically Base64-encoded in that parameter. Because the execution happened inside msdt.exe, a signed Microsoft binary with a legitimate purpose, it sidestepped the macro warnings and Protected View behaviour that users had been trained to treat as the danger signal.
The padding comment in the HTML existed to push the file over a size threshold, without which Office would not process the remote content — a small detail that tells you how carefully the technique had been worked out.
A sample was uploaded to VirusTotal from Belarus on 27 May 2022, and public analysis followed within hours. The uncomfortable part came next: researchers at the Shadow Chaser Group had reported the same issue to Microsoft on 12 April 2022, and the report had been closed as not a security issue. Earlier samples dating from 2021 were subsequently identified, indicating use in the wild long before disclosure.
Microsoft acknowledged the vulnerability on 30 May 2022 with a workaround — deleting the ms-msdt protocol handler registry key — and shipped a patch on 14 June 2022. In the interval, exploitation was broad: state-aligned groups targeting government bodies in Europe, including UK local authorities, alongside commodity criminal phishing campaigns delivering infostealers and ransomware loaders.
search-ms, ms-officecmd, and others have since been abused similarly.winword.exe or explorer.exe spawning msdt.exe — the same living off the land pattern seen elsewhere, and msdt.exe spawning PowerShell. That rule is generic, cheap, and catches variants of the technique that have nothing to do with this CVE.If you still hold telemetry from 2022, search for msdt.exe executions with command lines containing IT_BrowseForFile or PCWDiagnostic, for Office applications spawning msdt.exe, and for outbound HTTP requests made by Office processes to unfamiliar hosts. The same patterns remain valid detections for the broader family of protocol handler abuse.
We assess endpoint hardening, including handler exposure and macro and document controls, as part of our infrastructure and architecture review services.
No, and that was the point. The technique used an external object reference and the ms-msdt protocol handler rather than VBA, so no macro warning appeared and Protected View did not stop it. With the RTF variant, selecting the file in Windows Explorer so that the preview pane rendered it was sufficient, without the user opening anything.
Not on patched systems. Microsoft fixed it on 14 June 2022, and the interim workaround removed the vulnerable protocol handler entirely. The broader technique of abusing Windows URI handlers from documents remains current, with several similar issues found since, so the detection and hardening advice still applies even though this specific CVE does not.
Process ancestry. Alert when an Office application or Explorer spawns a diagnostic or scripting utility, and when such a utility spawns a command interpreter. These relationships are rare in legitimate use, easy to express as a rule, and remain effective against variants that use different handlers or different CVEs.
Audit them and remove what you do not need. Many registered URI schemes launch local applications with parameters an attacker can influence, and few are required on a corporate build. Removing unused handlers reduces this attack surface permanently. Test changes first, since some business applications depend on custom handlers for deep linking.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.