# CVE-2021-38647: Microsoft Open Management Infrastructure (OMI) Remote Code Execution

> Attackers can execute arbitrary code remotely on systems running Microsoft Open Management Infrastructure, affecting various Azure and System Center components.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2021
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-rp2g-5hw2-q565

## What is CVE-2021-38647?

CVE-2021-38647 is a critical code injection vulnerability in Microsoft Azure Automation State Configuration, DSC Extension, published on 15 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Open Management Infrastructure (OMI) Remote Code Execution Vulnerability

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

It affects 10 products.


Products: Microsoft Azure Automation State Configuration, Microsoft Azure Automation Update Management, Microsoft Azure Diagnostics \(Lad\), Microsoft Azure Security Center, Microsoft Azure Sentinel, Microsoft Azure Stack Hub, Microsoft Container Monitoring Solution, Microsoft Log Analytics Agent, Microsoft Open Management Infrastructure, Microsoft System Center Operations Manager.

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

No fix has been published for CVE-2021-38647 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 17 Nov 2021.

## Is CVE-2021-38647 being exploited?

Yes. Attackers have exploited CVE-2021-38647 in the wild since at least 3 Nov 2021, including in ransomware campaigns.

Public exploit code:

- Proof on Concept Exploit for CVE-2021-38647 (OMIGOD) (github_poc): https://github.com/horizon3ai/CVE-2021-38647
- CVE-2021-38647 - POC to exploit unauthenticated RCE #OMIGOD (github_poc): https://github.com/AlteredSecurity/CVE-2021-38647
- OMIGOD! OM I GOOD? A free scanner to detect VMs vulnerable to one of the "OMIGOD" vulnerabilities discovered by Wiz's threat research team, specifically CVE-2021-38647. (github_poc): https://github.com/marcosimioni/omigood
- CVE-2021-38647 POC for RCE (github_poc): https://github.com/midoxnet/CVE-2021-38647
- CVE-2021-38647 AKA "OMIGOD" vulnerability in Windows OMI  (github_poc): https://github.com/corelight/CVE-2021-38647
- OMIGod / CVE-2021-38647 POC and Demo environment (github_poc): https://github.com/SimenBai/CVE-2021-38647-POC-and-Demo-environment

## Other vulnerabilities in Microsoft Azure Automation State Configuration, DSC Extension

- [CVE-2021-38645](https://insights.sbomify.com/CVE-2021-38645/): Microsoft Open Management Infrastructure (OMI) Privilege Escalation (high 7.8, exploited in the wild)
- [CVE-2021-38648](https://insights.sbomify.com/CVE-2021-38648/): Microsoft Open Management Infrastructure (OMI) Privilege Escalation (high 7.8, exploited in the wild)
- [CVE-2021-38649](https://insights.sbomify.com/CVE-2021-38649/): Microsoft Open Management Infrastructure (OMI) Privilege Escalation (high 7.0, exploited in the wild)
- [CVE-2022-29149](https://insights.sbomify.com/CVE-2022-29149/): Open Management Infrastructure (OMI) Elevation of Privilege Vulnerability (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-38647 is a critical code injection vulnerability in Microsoft Azure Automation State Configuration, DSC Extension, published on 15 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2021-38647 in the wild since at least 3 Nov 2021, including in ransomware campaigns.

Affected product: Microsoft Azure Automation State Configuration, DSC Extension. 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-38647/ (Markdown: https://insights.sbomify.com/CVE-2021-38647/index.md)
```

## Sources

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

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