CyberSecBulletin
CVE-2023-20893NVD status: Modified

VMware vCenter Server (vCenter Server): Use After Free

CVE-2023-20893 is a critical-severity use after free vulnerability in VMware vCenter Server (vCenter Server) from VMware, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 8.0 U1b, 7.0 u3m as the first without the flaw, so updating VMware vCenter Server (vCenter Server) to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.25% chance of exploitation within 30 days, higher than 70% of scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update VMware vCenter Server (vCenter Server) to 8.0 U1b or 7.0 u3m, whichever matches your release line, or a later version.
  2. Update VMware Cloud Foundation (vCenter Server) to 7.0 U3m, 8.0 U1b or a later version.
  3. Update Vcenter Server to 7.0 or a later version.
  4. Read the advisory on vmware.com for workarounds and exact fixed builds.
  5. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
VMwareVMware vCenter Server (vCenter Server)8.0 up to, but not including, 8.0 U1b; 7.0 up to, but not including, 7.0 u3m8.0 U1b, 7.0 u3m
VMwareVMware Cloud Foundation (vCenter Server)5.x up to, but not including, 7.0 U3m, 8.0 U1b; 4.x up to, but not including, 7.0 U3m, 8.0 U1b7.0 U3m, 8.0 U1b
VMwareVcenter Serverbefore 7.0; 7.0; 8.07.0

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.18.1HighCNA (vmware.com)
CVSS 3.19.8CriticalNVD

Official description

The VMware vCenter Server contains a use-after-free vulnerability in the implementation of the DCERPC protocol. A malicious actor with network access to vCenter Server may exploit this issue to execute arbitrary code on the underlying operating system that hosts vCenter Server.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Use After Free

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

How developers prevent this class of flaw

  • Choose a language that provides automatic memory management.
  • When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.

More Use After Free vulnerabilities (CWE-416)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in VMware vCenter Server (vCenter Server)

All VMware vCenter Server (vCenter Server) vulnerabilities

Recent Use After Free vulnerabilities

Spotted an error? Tell us.