CVE DatabaseCVE-2021-38648
한국어 권고문 →
CVE-2021-386487.8/HIGHCISA KEV

Microsoft Open Management Infrastructure (OMI) Privilege Escalation and Authentication Bypass (CVE-2021-38648)

⚡ Jump to Patch
Affected Vendors
microsoft
Affected Components
open management infrastructure, omi
Published Date
2021-09-15
CVSS v3.1
7.8
HIGH
EPSS (30d)
11.4%
FIRST.org
CISA KEV
Exploited

Executive & SecOps Summary

SECOPS ASSESSMENT
Affected Scope

Microsoft Open Management Infrastructure (OMI) versions prior to 1.6.8-1, commonly deployed in Azure Linux environments

Impact

Remote or local attackers can bypass authentication to execute arbitrary commands with root privileges, leading to full system compromise

Mitigation

Immediately upgrade OMI to version 1.6.8-1 or higher, and restrict access to OMI ports (5985, 5986)

Affected Products & Version Scope

Microsoft Open Management Infrastructure (OMI) versions prior to 1.6.8-1

Remediation & Live Workaround Commands

PATCH & WORKAROUND

1. Official Patch & Version Upgrade Commands

Update the OMI package to the latest secure version (1.6.8-1 or higher) using the system package manager.

bash
# For Debian/Ubuntu-based systems
sudo apt-get update && sudo apt-get install --only-upgrade omi -y

# For RHEL/CentOS-based systems
sudo yum update omi -y

2. Temporary Workaround & Hardening Configuration

If patching cannot be applied immediately, restrict network access to the OMI ports (5985, 5986) using host-based firewalls.

bash
# Block OMI ports using iptables
sudo iptables -A INPUT -p tcp --dport 5985 -j DROP
sudo iptables -A INPUT -p tcp --dport 5986 -j DROP

# Block OMI ports using ufw
sudo ufw deny proto tcp from any to any port 5985,5986
sudo ufw reload

3. Log Audit & IoC Verification Commands

Verify the installed OMI version and check if the OMI service is listening on external ports.

bash
# Check OMI version
if [ -f /opt/omi/bin/omiserver ]; then
    /opt/omi/bin/omiserver -v
else
    echo 'OMI is not installed or not in the default path.'
fi

# Check if OMI ports are listening
sudo ss -tulnp | grep -E '5985|5986'
Interactive SecOps Remediation Checklist
0/4 (0%)
Recommended Security Control & Mitigation Partner
Datadog Cloud & Kubernetes Security
Audit all Azure and on-premises Linux instances for OMI, upgrade to version 1.6.8-1+, and block ports 5985/5986 from external access.

Detect Container Escape & Privilege Escalation Across Your Kubernetes Fleet

Continuous eBPF-based runtime threat detection and posture management for AWS, GCP, Azure, Docker, and Kubernetes workloads.

Real-Time Production Container CVE Mapping

Technical Root Cause & Exploitation Mechanics

1. Vulnerability Overview & Root Cause

This vulnerability, widely known as 'OMIGOD', is a critical authentication bypass and elevation of privilege vulnerability in Microsoft's Open Management Infrastructure (OMI). OMI is an open-source CIM management server for Linux systems, frequently pre-installed and automatically deployed in Azure Linux Virtual Machines. The root cause lies in a flaw within the OMI authentication handler: when an HTTP/HTTPS request is received with a missing or empty 'Authorization' header, the server incorrectly defaults to treating the request as pre-authenticated with administrative privileges.

2. Exploitation Mechanics & Attack Scenario

An attacker can exploit this vulnerability by sending a specially crafted SOAP request over HTTP/HTTPS to the OMI listening ports (typically 5985 or 5986). By omitting the 'Authorization' header from the request, the OMI server processes the command under the context of the privileged 'root' user. This allows unauthenticated remote attackers to execute arbitrary code (RCE) if the ports are exposed to the internet, or local users to escalate privileges to root (LPE).

3. Infrastructure & Business Impact

This vulnerability is actively exploited in the wild and is cataloged in CISA's Known Exploited Vulnerabilities (KEV). Given OMI's silent deployment across millions of Azure Linux VMs, the business impact is severe. Successful exploitation allows attackers to gain full administrative control over cloud infrastructure, enabling lateral movement, data exfiltration, ransomware deployment, and unauthorized resource utilization.

Official Vendor Advisories & References

Frequently Asked SecOps Questions (CVE-2021-38648)

FAQ

Q1. How critical is CVE-2021-38648 and is it actively exploited in the wild?

CVE-2021-38648 is rated CVSS 7.8 (HIGH) with a 30-day EPSS exploitation probability of 11.4%. It is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, requiring immediate emergency remediation.

Q2. Which vendors and products are affected by CVE-2021-38648?

Primary impacted vendors include microsoft across open management infrastructure, omi. Scope summary: Microsoft Open Management Infrastructure (OMI) versions prior to 1.6.8-1

Q3. What temporary mitigations or workarounds exist for CVE-2021-38648 before patching?

[Mitigation] Immediately upgrade OMI to version 1.6.8-1 or higher, and restrict access to OMI ports (5985, 5986) Follow the CLI remediation commands and interactive SecOps checklist on this page to restrict exposure prior to your maintenance window.

SECOPS WORKBENCH INTEGRATION

Generate an Internal Engineering Notice or CISO Report for CVE-2021-38648

Instantly format this advisory into an executive CISO summary or engineering patch ticket.

Generate Report →

🔗 Related Advisories in Similar Stack (microsoft)

View Category →
SecOps Advisory Dispatch & RSS Feed

Subscribe to Daily Vulnerability Briefings & KEV Alerts

Concise morning briefings for SecOps, DevSecOps, and SRE teams covering newly exploited CVEs and mitigation priorities.

Slack / Teams / RSS Feed:
PatchKO
CVE-2021-38648 Microsoft Open Management Infrastructure (OMI) Privilege Escalation and Authentication Bypass (CVE-2021-38648) (CVSS 7.8) - Patch & Workaround | CVE Pulse