CVE-2023-36737

7.8 HIGH

📋 TL;DR

This vulnerability allows an authenticated attacker with local access to an Azure virtual machine to elevate privileges to SYSTEM level through the Network Watcher VM Agent. It affects Azure virtual machines running Windows with the Network Watcher extension installed.

💻 Affected Systems

Products:
  • Microsoft Azure Network Watcher VM Agent
Versions: Versions prior to the fix released in September 2023
Operating Systems: Windows
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects Azure VMs with the Network Watcher extension installed (commonly enabled by default in many Azure deployments).

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Full SYSTEM-level compromise of the Azure VM, enabling complete control over the system, data exfiltration, lateral movement, and persistence establishment.

🟠

Likely Case

Privilege escalation from a standard user or lower-privileged service account to SYSTEM, allowing installation of malware, credential theft, and further exploitation.

🟢

If Mitigated

Limited impact due to proper access controls, network segmentation, and monitoring preventing successful exploitation or containing damage.

🌐 Internet-Facing: LOW - Exploitation requires local authenticated access to the VM, not directly reachable from the internet.
🏢 Internal Only: HIGH - Attackers with initial access to Azure VMs (via compromised accounts, phishing, etc.) can exploit this for privilege escalation.

🎯 Exploit Status

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

Exploitation requires authenticated local access to the VM. Microsoft has not disclosed technical details publicly.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Updated Network Watcher agent version (automatic update via Azure platform)

Vendor Advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-36737

Restart Required: No

Instructions:

1. Ensure Azure VMs are set to automatically update extensions. 2. For manual update, redeploy the Network Watcher extension via Azure Portal, CLI, or PowerShell. 3. Verify the agent version is updated post-deployment.

🔧 Temporary Workarounds

Disable Network Watcher Extension

all

Remove the vulnerable extension if not required for monitoring.

az vm extension delete --resource-group <RG> --vm-name <VM> --name NetworkWatcherAgentWindows

Restrict Local Access

windows

Implement strict access controls and least privilege for Azure VM local accounts.

🧯 If You Can't Patch

  • Implement network segmentation to isolate vulnerable VMs from critical assets.
  • Enable enhanced monitoring and alerting for privilege escalation attempts on Azure VMs.

🔍 How to Verify

Check if Vulnerable:

Check if Network Watcher extension is installed on Windows Azure VMs via Azure Portal (Extensions blade) or CLI: az vm extension list --resource-group <RG> --vm-name <VM>

Check Version:

az vm extension show --resource-group <RG> --vm-name <VM> --name NetworkWatcherAgentWindows

Verify Fix Applied:

Verify the extension version is updated (post-September 2023) and no longer listed as vulnerable in Azure Security Center.

📡 Detection & Monitoring

Log Indicators:

  • Windows Event Logs: Unexpected process creation with SYSTEM privileges, especially from Network Watcher agent paths.
  • Azure Activity Logs: Unusual extension modifications or privilege escalation patterns.

Network Indicators:

  • Unusual outbound connections from VMs post-exploitation (e.g., to command-and-control servers).

SIEM Query:

Example for Azure Sentinel: SecurityEvent | where EventID == 4688 | where NewProcessName contains "NetworkWatcher" | where SubjectUserName != "SYSTEM"

🔗 References

📤 Share & Export