CVE-2024-30076

6.8 MEDIUM

📋 TL;DR

This vulnerability allows an authenticated attacker to escalate privileges within Windows Container Manager Service. Attackers could gain SYSTEM-level access on affected Windows systems. Only systems running Windows with Container Manager Service enabled are affected.

💻 Affected Systems

Products:
  • Windows Container Manager Service
Versions: Windows 10, Windows 11, Windows Server 2019, Windows Server 2022 (specific versions as per Microsoft advisory)
Operating Systems: Windows
Default Config Vulnerable: ⚠️ Yes
Notes: Requires Container Manager Service to be running; typically affects systems using Windows containers or related features.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Full system compromise with SYSTEM privileges, enabling complete control over the host, installation of malware, data theft, and lateral movement.

🟠

Likely Case

Privilege escalation from a lower-privileged user account to SYSTEM, allowing attackers to bypass security controls and execute arbitrary code.

🟢

If Mitigated

Limited impact if proper access controls, least privilege principles, and network segmentation are implemented to restrict container service access.

🌐 Internet-Facing: LOW
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Exploitation requires local access and authentication; no public exploit code is known at this time.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Apply the latest Windows security updates from Microsoft (specific KB numbers in the advisory)

Vendor Advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-30076

Restart Required: Yes

Instructions:

1. Open Windows Update settings
2. Check for updates and install all available security updates
3. Restart the system as prompted

🔧 Temporary Workarounds

Disable Windows Container Manager Service

windows

Stop and disable the Container Manager Service if not required, reducing the attack surface.

sc stop cmsvc
sc config cmsvc start= disabled

🧯 If You Can't Patch

  • Restrict access to systems running Container Manager Service using network segmentation and firewall rules.
  • Implement strict least privilege principles to limit user accounts that can interact with container services.

🔍 How to Verify

Check if Vulnerable:

Check if the system is running a vulnerable version of Windows and has Container Manager Service enabled via 'sc query cmsvc'.

Check Version:

winver

Verify Fix Applied:

Verify that Windows Update history shows the relevant security update installed and that the system version matches the patched version.

📡 Detection & Monitoring

Log Indicators:

  • Unusual privilege escalation events in Windows Security logs (Event ID 4672, 4688)
  • Suspicious service manipulation attempts in System logs

Network Indicators:

  • Unexpected network connections from container-related processes

SIEM Query:

EventID=4672 OR EventID=4688 | where ProcessName contains 'cmsvc' OR CommandLine contains container-related terms

🔗 References

📤 Share & Export