Threats / Broadcom / CVE-2024-37079
CVE-2024-37079
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Broadcom VMware vCenter Server vulnerability
Broadcom VMware vCenter Server contains an out-of-bounds write vulnerability in DCERPC protocol handling that allows remote code execution via specially crafted network packets.
Verdict
Today item — known-exploited.
A network-accessible out-of-bounds write in vCenter Server's DCERPC implementation enables unauthenticated remote code execution. Active exploitation in the wild increases urgency for patching.
CISA KEV Yes · 2026-01-235EPSS 0.22377 (verify live)6CVSS 9.83CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
3 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 2026-01-23).
Probability (EPSS)
EPSS 0.22377 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Broadcom, VMware vCenter Server. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-787 Out-of-bounds Write — weakness family: Memory safety.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 584 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution 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 board1
Front door — unauthenticated access narrative 1
Attacker
I craft malicious DCERPC protocol packets targeting vCenter Server's network interface.
Business
Attackers gain initial network foothold without authentication requirements.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I trigger the out-of-bounds write condition to corrupt memory and achieve code execution.
Business
Attackers execute arbitrary code with vCenter Server process privileges.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistence and lateral movement within the virtualized infrastructure.
Business
Entire virtual machine fleet and hosted workloads become compromised and controllable.
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