WorkstationApplication · VMware
CVE-2024-22269
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 · uneditedVMware Workstation and Fusion contain an information disclosure vulnerability in the vbluetooth device. A malicious actor with local administrative privileges on a virtual machine may be able to read privileged information contained in hypervisor memory from a virtual machine.
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 confidenceVMware Workstation and Fusion contain an information disclosure vulnerability in the vbluetooth virtual device. A malicious actor with local administrative privileges on a guest virtual machine can read privileged information from hypervisor memory, potentially allowing escape from the VM isolation to access sensitive host data.
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
WorkstationApplication
>= 17.0.0, < 17.5.2
FusionApplication
>= 13.0.0, < 13.5.2CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Check VMware Workstation versionOpen Workstation, go to Help > About VMware Workstation, or run 'vmware -v' from command lineAffected if Version is 17.0.0 through 17.5.1 (inclusive)
-
Check VMware Fusion versionOpen Fusion, go to VMware Fusion menu > About VMware Fusion, or run 'vmrun -version'Affected if Version is 13.0.0 through 13.5.1 (inclusive)
-
Identify VMs with vbluetooth deviceOpen VM settings, expand each VM and look for Bluetooth devices under Hardware, or examine VMX configuration files for 'bluetooth.*' linesAffected if Any guest VM has a Bluetooth virtual device configured or attached
A user is affected if they run vulnerable Workstation (17.0.0-17.5.1) or Fusion (13.0.0-13.5.1) AND have Bluetooth virtual devices enabled in guest VMs with administrative access granted.
Generated from the published advisory. Verify against your own configuration.
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 · scoped13.5.217.5.2
Apply the VMware security patches for Workstation and Fusion to address this vulnerability. Until patched, limit administrative access to virtual machines and monitor for suspicious activity.
VMware Workstation 17.5.2 or VMware Fusion 13.5.2
- Ensure all virtual machines are powered off and backed up if needed
- Download VMware Workstation 17.5.2 or later from the Broadcom support portal (support.broadcom.com)
- Download VMware Fusion 13.5.2 or later from the Broadcom support portal if using Fusion
- Uninstall the current version of VMware Workstation or Fusion
- Install the updated version (Workstation 17.5.2+ or Fusion 13.5.2+)
- Restart the host system after installation
- Power on virtual machines and verify normal operation
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Workstation
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22269 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-22269 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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