CVE-2023-34044
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( 17.x prior to 17.5) and Fusion(13.x prior to 13.5) contain an out-of-bounds read vulnerability that exists in the functionality for sharing host Bluetooth devices with the virtual machine. 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 (17.x prior to 17.5) and Fusion (13.x prior to 13.5) contain an out-of-bounds read vulnerability in the Bluetooth device sharing functionality. A malicious actor with local administrative privileges on a guest virtual machine can read privileged information from hypervisor memory due to the improper bounds checking.
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>= 17.0.0, < 17.5>= 13.0.0, < 13.5CVSS 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.
-
Identify VMware product installationOn Windows, check Program Files/VMware for VMware Workstation folders. On macOS, check /Applications for VMware Fusion.app. Alternatively, run 'vmware -v' from command line.Affected if Neither VMware Workstation nor Fusion is installed (not affected).
-
Check installed VMware versionRun 'vmware -v' on Windows or 'vmware --version' on macOS, or right-click the VMware application in Add/Remove Programs (Windows) or Finder (macOS) to view version information.Affected if Version is 17.0.0 through 17.4.x for Workstation, or 13.0.0 through 13.4.x for Fusion.
-
Verify Bluetooth device sharing configurationOpen VMware settings for any configured VM, navigate to VM > Settings > Hardware > Bluetooth, or check if Bluetooth devices are added to the guest VM configuration.Affected if Bluetooth device sharing is configured and active for any guest VM.
-
Confirm guest VM administrative access existsReview guest VM user accounts and permissions. Check if any user on the guest has administrative/root privileges, as the attacker needs local admin rights on the guest.Affected if Guest virtual machines have users with local administrative privileges.
You are affected if VMware Workstation 17.0.0-17.4.x or Fusion 13.0.0-13.4.x is installed AND Bluetooth device sharing is enabled for a guest VM that has users with administrative privileges.
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.517.5
Upgrade VMware Workstation to version 17.5 or later, and Fusion to version 13.5 or later, to obtain the security patch for this vulnerability.
VMware Workstation 17.5 or VMware Fusion 13.5
- Back up all virtual machines before proceeding with the update
- Download VMware Workstation 17.5 (for Workstation users) or VMware Fusion 13.5 (for Fusion users) from the official VMware website
- Verify the integrity of the downloaded installer using the provided checksums
- Power off all running virtual machines
- Install the updated version of VMware Workstation or Fusion
- Restart the host computer to ensure all hypervisor components are properly loaded
- After restart, verify the installed version is 17.5 or later (Workstation) or 13.5 or later (Fusion)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34044 — 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-2023-34044 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