# CVE-2021-31200: Common Utilities Remote Code Execution Vulnerability

> An attacker can execute arbitrary code via the Microsoft Common Utilities library, requiring immediate patching by developers using this component.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-9m4f-6g7p-8g3m

## What is CVE-2021-31200?

CVE-2021-31200 is a high-severity code injection vulnerability in Microsoft common_utils.py, published on 11 May 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Common Utilities Remote Code Execution Vulnerability

## Which versions are affected by CVE-2021-31200?

It affects 1 product.


Products: Microsoft Neural Network Intelligence.

## How do I fix CVE-2021-31200?

No fix has been published for CVE-2021-31200 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-31200 being exploited?

There is no known exploitation of CVE-2021-31200 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-31200 and fix it if it is affected.

What it is: CVE-2021-31200 is a high-severity code injection vulnerability in Microsoft common_utils.py, published on 11 May 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-31200 in the wild and no public exploit code.

Affected product: Microsoft common_utils.py. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2021-31200/ (Markdown: https://insights.sbomify.com/CVE-2021-31200/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-31200
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-31200
- OSV: https://osv.dev/vulnerability/CVE-2021-31200

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