# GSD-2022-30190: From the original tweet: Interesting maldoc was submitted from Belarus.

> Attackers can execute arbitrary code via malicious Office documents using the ms-msdt protocol, requiring user interaction to open the file.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 May 2022

## What is GSD-2022-30190?

GSD-2022-30190 is a code injection vulnerability, published on 31 May 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

From the original tweet: Interesting maldoc was submitted from Belarus. It uses Word's external link to load the HTML and then uses the "ms-msdt" scheme to execute PowerShell code. 

 From Microsoft: 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. This issue has been nicknamed "Follina "

## Which versions are affected by GSD-2022-30190?


## How do I fix GSD-2022-30190?

No fix has been published for GSD-2022-30190 yet. Limit exposure of the affected software until one is available.

## Is GSD-2022-30190 being exploited?

There is no known exploitation of GSD-2022-30190 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GSD-2022-30190 and fix it if it is affected.

What it is: GSD-2022-30190 is a code injection vulnerability, published on 31 May 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GSD-2022-30190 in the wild and no public exploit code.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GSD-2022-30190/ (Markdown: https://insights.sbomify.com/GSD-2022-30190/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GSD-2022-30190

---
From sbomify Insights: https://insights.sbomify.com/GSD-2022-30190/
Summaries are generated and may contain mistakes; the official description above is the record.