dbcve.org
FusionApplication · VMware

CVE-2024-22267

HIGH · 8.2 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 13.5.2 / 17.5.2 or later.
See remediation →
84/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
VMware Workstation and Fusion contain a use-after-free vulnerability in the vbluetooth device. A malicious actor with local administrative privileges on a virtual machine may exploit this issue to execute code as the virtual machine's VMX process running on the host.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A use-after-free vulnerability exists in the vbluetooth virtual device of VMware Workstation and Fusion. An attacker with local administrative privileges inside a guest virtual machine can exploit this memory corruption issue to achieve code execution in the VMX process running on the host system, effectively breaking out of the guest isolation.

MitigationApply the vendor-supplied security patches for VMware Workstation and Fusion. Until patches are applied, limit administrative access to virtual machines and avoid granting unnecessary privileges to untrusted users.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FusionApplication
Affected:>= 13.0.0, < 13.5.2
WorkstationApplication
Affected:>= 17.0.0, < 17.5.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed VMware product
    On macOS (Fusion): open a terminal and run 'vmware -v' or check /Applications/VMware Fusion.app. On Windows (Workstation): open Command Prompt or PowerShell and run 'vmware -v' or check Program Files/VMware/VMware Workstation. On Linux: run 'vmware -v' or check /usr/bin/vmware.
    Affected if The product is VMware Fusion or VMware Workstation with version >= 17.0.0 or >= 13.0.0 respectively, but < 13.5.2 or < 17.5.2
  2. Confirm the exact version number
    Compare your installed version to the affected ranges: Fusion 13.0.0 through 13.5.1 (excluding 13.5.2), Workstation 17.0.0 through 17.5.1 (excluding 17.5.2). Use 'vmware -v' output to verify.
    Affected if The installed version falls within >= 13.0.0 and < 13.5.2 for Fusion, or >= 17.0.0 and < 17.5.2 for Workstation
  3. Check if vbluetooth virtual device is present
    Inspect the VMX configuration file of any guest virtual machine (located in the VM bundle/folder with .vmx extension). Look for entries containing 'vbluetooth' such as 'vbluetooth.present = "TRUE"' or 'usb.vbluetooth.present = "TRUE"'. Alternatively, in Fusion go to Virtual Machine Settings > Hardware and check for Bluetooth device presence.
    Affected if The vbluetooth virtual device is present and connected to the guest VM (vbluetooth.present = TRUE)
  4. Verify guest VM has administrative privileges
    Review user access within the guest virtual machine. Check if any user account inside the guest VM has administrative/root privileges (sudoers, Administrators group, or equivalent). This can be done by examining /etc/sudoers (Linux) or checking Local Users and Groups (Windows) inside the guest OS.
    Affected if Any user inside the guest virtual machine has local administrative or root-level privileges

You are affected if you run VMware Fusion < 13.5.2 or Workstation < 17.5.2 with the vbluetooth virtual device enabled in a guest VM where untrusted users have administrative access inside that guest.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 13.5.2 / 17.5.2 or later
Fixed in 13.5.217.5.2
Interim mitigation

Apply the vendor-supplied security patches for VMware Workstation and Fusion. Until patches are applied, limit administrative access to virtual machines and avoid granting unnecessary privileges to untrusted users.

Recommended fix High confidence

VMware Workstation 17.5.2 or Fusion 13.5.2

  1. Identify whether VMware Workstation or Fusion (or both) is installed
  2. Download the fixed version from Broadcom's support portal at support.broadcom.com
  3. Ensure all running virtual machines are powered off
  4. Backup virtual machine configurations if desired
  5. Uninstall the current version of VMware Workstation or Fusion
  6. Install the fixed version (Workstation 17.5.2 or Fusion 13.5.2)
  7. Restart the host system after installation
  8. Power on virtual machines and verify normal operation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fusion Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22267 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-22267 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data