How severe is CVE-2024-38813?

CVE-2024-38813 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2024-38813 being actively exploited?

Yes. CVE-2024-38813 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2024-11-20, which means active exploitation has been confirmed. It should be prioritised for remediation.

What products are affected by CVE-2024-38813?

CVE-2024-38813 primarily affects Vmware Cloud Foundation. In total, 49 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2024-38813?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.

Does CVE-2024-38813 have an EU (EUVD) identifier?

Yes. CVE-2024-38813 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-37704. It is also flagged as exploited in the EUVD (since 2024-11-20).

When was CVE-2024-38813 published?

CVE-2024-38813 was published on 2024-09-17 and last updated on 2026-06-17.

CVE-2024-38813

CVE-2024-38813 is a high-severity vulnerability in Vmware Cloud Foundation with a CVSS 3.x base score of 7.5. It is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, confirming it has been exploited in the wild (added 2024-11-20). The underlying weakness is classified as CWE-273.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 17% (97th percentile)
Actively exploited: Yes — listed in CISA KEV (added 2024-11-20)
EU (EUVD) id: EUVD-2024-37704
EU exploitation: Flagged exploited in the ENISA EU Vulnerability Database (since 2024-11-20)
Weakness: CWE-273
Affected product: Vmware Cloud Foundation
Published: 2024-09-17
Last modified: 2026-06-17

Description

The vCenter Server contains a privilege escalation vulnerability. A malicious actor with network access to vCenter Server may trigger this vulnerability to escalate privileges to root by sending a specially crafted network packet.

Frequently asked questions

What is CVE-2024-38813?: The vCenter Server contains a privilege escalation vulnerability. A malicious actor with network access to vCenter Server may trigger this vulnerability to escalate privileges to root by sending a specially crafted network packet.
How severe is CVE-2024-38813?: CVE-2024-38813 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2024-38813 being actively exploited?: Yes. CVE-2024-38813 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2024-11-20, which means active exploitation has been confirmed. It should be prioritised for remediation.
What products are affected by CVE-2024-38813?: CVE-2024-38813 primarily affects Vmware Cloud Foundation. In total, 49 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2024-38813?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.
Does CVE-2024-38813 have an EU (EUVD) identifier?: Yes. CVE-2024-38813 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-37704. It is also flagged as exploited in the EUVD (since 2024-11-20).
When was CVE-2024-38813 published?: CVE-2024-38813 was published on 2024-09-17 and last updated on 2026-06-17.

References

Affected products (49)

cpe:2.3:a:vmware:cloud_foundation:*:*:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:-:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:a:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:b:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:c:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:d:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update1:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update1a:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update1c:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update1d:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update2:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update2a:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update2b:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update2c:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update2d:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update3:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update3a:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update3c:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update3d:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update3e:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update3f:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update3g:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update3h:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update3i:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update3j:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update3k:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update3l:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update3m:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update3n:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update3o:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update3p:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update3q:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update3r:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:7.0:update3s:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:8.0:-:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:8.0:a:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:8.0:b:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:8.0:c:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:8.0:update1:*:*:*:*:*:*
cpe:2.3:a:vmware:vcenter_server:8.0:update1a:*:*:*:*:*:*

More vulnerabilities in Vmware Cloud Foundation

CVE-2023-34063 — Critical (CVSS 9.9): Aria Automation contains a Missing Access Control vulnerability. An authenticated malicious actor may exploit this…
CVE-2024-38812 — Critical (CVSS 9.8): The vCenter Server contains a heap-overflow vulnerability in the implementation of the DCERPC protocol. A malicious…
CVE-2024-37079 — Critical (CVSS 9.8): vCenter Server contains a heap-overflow vulnerability in the implementation of the DCERPC protocol. A malicious actor…
CVE-2023-20864 — Critical (CVSS 9.8): VMware Aria Operations for Logs contains a deserialization vulnerability. An unauthenticated, malicious actor with…
CVE-2022-22972 — Critical (CVSS 9.8): VMware Workspace ONE Access, Identity Manager and vRealize Automation contain an authentication bypass vulnerability…
CVE-2022-22954 — Critical (CVSS 9.8): VMware Workspace ONE Access and Identity Manager contain a remote code execution vulnerability due to server-side…

All CVEs affecting Vmware Cloud Foundation →

Other CWE-273 vulnerabilities

CVE-2015-0278 — Critical (CVSS 10.0): libuv before 0.10.34 does not properly drop group privileges, which allows context-dependent attackers to gain…
CVE-2023-34844 — Critical (CVSS 9.8): Play With Docker < 0.0.2 has an insecure CAP_SYS_ADMIN privileged mode causing the docker container to escape.
CVE-2021-36372 — Critical (CVSS 9.8): In Apache Ozone versions prior to 1.2.0, Initially generated block tokens are persisted to the metadata database and…
CVE-2020-24361 — Critical (CVSS 9.8): SNMPTT before 1.4.2 allows attackers to execute shell code via EXEC, PREXEC, or unknown_trap_exec.
CVE-2011-3350 — Critical (CVSS 9.8): masqmail 0.2.21 through 0.2.30 improperly calls seteuid() in src/log.c and src/masqmail.c that results in improper…
CVE-2011-2921 — Critical (CVSS 9.8): ktsuss versions 1.4 and prior has the uid set to root and does not drop privileges prior to executing user specified…

Browse all CWE-273 vulnerabilities →