CVE-2024-37079

VMware vCenter Server Out-of-bounds Write (CVE-2024-37079)

Detects exploitation attempts targeting CVE-2024-37079, an out-of-bounds write vulnerability (CWE-787) in Broadcom VMware vCenter Server. This KEV-listed vulnerability allows unauthenticated remote attackers to trigger memory corruption via malformed DCERPC requests to the vCenter management interface, potentially leading to remote code execution with SYSTEM-level privileges on the vCenter appliance.

Vulnerability Intelligence

KEV — Known Exploited

Affected Software

Vendor
Broadcom
Product
VMware vCenter Server

Weakness (CWE)

Timeline

Disclosed
January 23, 2026

CVSS

Unscored
Write-up coming soon

What is CVE-2024-37079 VMware vCenter Server Out-of-bounds Write (CVE-2024-37079)?

VMware vCenter Server Out-of-bounds Write (CVE-2024-37079) (CVE-2024-37079) maps to the Initial Access and Execution and Lateral Movement tactics — the adversary is trying to get into your network in MITRE ATT&CK.

This page provides production-ready detection logic for VMware vCenter Server Out-of-bounds Write (CVE-2024-37079), covering the data sources and telemetry it touches: CommonSecurityLog, Syslog, AzureActivity. The queries below are rated critical severity at medium confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.

MITRE ATT&CK

Tactic
Initial Access Execution Lateral Movement
Microsoft Sentinel / Defender
kusto
let vcenter_ips = dynamic([]);
union
(
    CommonSecurityLog
    | where DeviceProduct has_any ("vCenter", "VMware vCenter")
    | where Message has_any ("out-of-bounds", "heap corruption", "DCERPC", "vmdir", "vpxd crash", "core dump", "segfault")
    | project TimeGenerated, DeviceAddress, SourceIP, DestinationIP, Message, Activity, DeviceProduct
),
(
    Syslog
    | where ProcessName in ("vpxd", "vmdir", "vmdird", "vmafdd")
    | where SyslogMessage has_any ("segfault", "core dumped", "heap-buffer-overflow", "stack smashing", "SIGABRT", "SIGSEGV")
    | project TimeGenerated, HostName, HostIP, ProcessName, SyslogMessage
),
(
    AzureActivity
    | where ResourceProviderValue =~ "Microsoft.AVS"
    | where OperationNameValue has_any ("write", "update") and ActivityStatusValue =~ "Failed"
    | project TimeGenerated, CallerIpAddress, ResourceGroup, OperationNameValue, ActivityStatusValue
),
(
    CommonSecurityLog
    | where DestinationPort in (443, 902, 5480, 9443)
    | where DeviceVendor has_any ("VMware", "Broadcom")
    | where Activity has_any ("exploit", "attack", "CVE-2024-37079")
    | project TimeGenerated, SourceIP, DestinationIP, DestinationPort, Activity, Message
)
| sort by TimeGenerated desc

Detects indicators of CVE-2024-37079 exploitation against VMware vCenter Server by correlating vCenter process crashes, out-of-bounds memory errors, and anomalous DCERPC/management-port activity sourced from CommonSecurityLog and Syslog tables in Microsoft Sentinel.

critical severity medium confidence

Data Sources

CommonSecurityLog Syslog AzureActivity

Required Tables

CommonSecurityLog Syslog AzureActivity

False Positives

  • Legitimate vCenter upgrades or patches that cause transient service restarts may trigger process crash signals
  • Misconfigured third-party backup agents polling vCenter management APIs on non-standard schedules
  • Internal vulnerability scanners (Tenable, Qualys) probing vCenter management ports during authorized assessments
  • Hardware failures or resource exhaustion causing vCenter daemon crashes unrelated to exploitation

Sigma rule & cross-platform mapping

The detection logic for VMware vCenter Server Out-of-bounds Write (CVE-2024-37079) (CVE-2024-37079) above is provided in a vendor-neutral form so you can deploy it on any SIEM. The same logic is shipped here as native KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the following logsource:

logsource:
  product: azure

Browse the community-maintained Sigma rules for this technique:


Testing Methodology

Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Simulate vCenter DCERPC Malformed Request (Lab Only)

    Expected signal: Network flow log entry showing TCP connection attempt to target:135 with large payload; vCenter DCERPC service log entry showing parse error or malformed packet rejection

  2. Test 2Trigger vCenter vpxd Process Crash via Resource Exhaustion (Lab Only)

    Expected signal: Syslog entry on vCenter appliance: vpxd[PID]: segfault at [address]; core dump file created at /var/core/vpxd-[timestamp].core

  3. Test 3Probe vCenter Management Ports from Unauthorized IP (Lab Only)

    Expected signal: Firewall/network logs showing TCP SYN packets from scanner IP to vCenter management ports; vCenter access logs showing connection attempts to /ui, /sdk, VAMI endpoints

  4. Test 4Validate vCenter Log Forwarding and Crash Pattern Matching

    Expected signal: Syslog message appearing in SIEM ingestion pipeline with process name vpxd and severity daemon.crit containing the synthetic crash string

Unlock Pro Content

Get the full detection package for CVE-2024-37079 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections