basicsecurity.net
Proof, not just disclosure.
Threats / VMware / CVE-2024-38813
CVE-2024-38813 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

VMware vCenter Server vulnerability

VMware vCenter Server contains an improper privilege-drop check vulnerability allowing network-based attackers to escalate privileges to root via specially crafted packets.

Verdict

Today item — known-exploited.

A network-accessible privilege escalation flaw in vCenter Server permits unauthenticated or low-privileged attackers to gain root-level control. Active exploitation in the wild increases operational risk for virtualization infrastructure.

CISA KEV Yes · 2024-11-203EPSS 0.1462 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
6 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 2024-11-20).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.1462 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: VMware, vCenter Server. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-250 Excessive Privileges, CWE-273 CWE-273 — weakness family: Authorization / access control.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-250 · Excessive PrivilegesCWE-273 · CWE-273Authorization / access control
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious network packet targeting the privilege-drop validation logic in vCenter Server.
Business
Attacker gains initial network foothold against virtualization management infrastructure.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I exploit the improper privilege check to bypass security controls and escalate my access level.
Business
Attacker transitions from limited access to root-level control of the vCenter instance.
3

Lateral reach — past segmentation narrative 3

Attacker
I achieve root privileges on the vCenter Server, enabling full system compromise.
Business
Complete control of virtualization platform allows attacker to access, modify, or destroy all hosted virtual machines and data.
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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 6 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by vmware (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by vmwareCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.