basicsecurity.net
Proof, not just disclosure.
Threats / Microsoft / CVE-2021-38647
CVE-2021-38647 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Microsoft Open Management Infrastructure (OMI) vulnerability

Microsoft Open Management Infrastructure (OMI) in Azure VM Management Extensions contains a remote code execution vulnerability exploited in active ransomware campaigns.

Verdict

Today item, not a backlog item.

An unspecified vulnerability in OMI allows unauthenticated remote code execution on affected Azure virtual machines. Active exploitation in ransomware operations and high EPSS score indicate immediate risk to cloud infrastructure.

CISA KEV Yes · 2021-11-033Ransomware use Flagged3EPSS 0.99723 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
650 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), flagged for known ransomware use.
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.99723 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Microsoft, Open Management Infrastructure (OMI). Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-1390 CWE-1390.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I identify and scan for exposed OMI instances on Azure VMs accessible over the network.
Business
Attackers gain initial access to cloud infrastructure without credentials, bypassing perimeter controls.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I exploit the unspecified vulnerability to execute arbitrary code with system privileges on the target VM.
Business
Complete compromise of individual virtual machines enables lateral movement and data exfiltration.
3

Lateral reach — past segmentation narrative 3

Attacker
I deploy ransomware payloads and establish persistence across the compromised infrastructure.
Business
Widespread encryption of business-critical systems and backups results in operational shutdown and extortion demands.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • Ransomware-use flag (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 650 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by microsoft (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by microsoftCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.