FusionApplication · VMware

CVE-2020-3948

HIGH · 7.8 CVSS v3.1 Published 2020-03-16
Fix available
A fix is available. Upgrade to 11.5.2 / 15.5.2 or later.
See remediation →
80/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
Linux Guest VMs running on VMware Workstation (15.x before 15.5.2) and Fusion (11.x before 11.5.2) contain a local privilege escalation vulnerability due to improper file permissions in Cortado Thinprint. Local attackers with non-administrative access to a Linux guest VM with virtual printing enabled may exploit this issue to elevate their privileges to root on the same guest VM.

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

Linux guest VMs on vulnerable VMware Workstation (pre-15.5.2) and Fusion (pre-11.5.2) contain a local privilege escalation flaw in Cortado Thinprint's virtual printing component. Improper file permissions allow non-administrative local users to gain root access within the guest VM by exploiting the virtual printing feature.

MitigationApply VMware Workstation update 15.5.2 or later, and Fusion 11.5.2 or later to the host system. Alternatively, disable virtual printing in the guest VM settings as a workaround until patching is complete.

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:>= 11.0.0, < 11.5.2
WorkstationApplication
Affected:>= 15.0.0, < 15.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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. Verify VMware product is installed on the host
    Check for installed VMware Workstation or Fusion: On Windows, look in Program Files for 'VMware' folder or check Programs and Features; On macOS, check /Applications for VMware Fusion.app; On Linux, check /usr/bin/vmware or package manager listings
    Affected if Either VMware Workstation or VMware Fusion is installed on the system
  2. Check VMware Workstation version
    Open Workstation, go to Help > About VMware Workstation, or run 'vmware -v' from command line. Compare the version number against the affected range
    Affected if Installed version is 15.0.0 or higher but lower than 15.5.2
  3. Check VMware Fusion version
    Open Fusion, go to VMware Fusion menu > About VMware Fusion, or run 'vmware -v' in Terminal. Compare the version number against the affected range
    Affected if Installed version is 11.0.0 or higher but lower than 11.5.2
  4. Identify if any guest VMs have virtual printing enabled
    Open VM settings in affected VMware product: For Workstation, go to VM > Settings > Options > Shared Folders (virtual printing option may appear here or under printer configuration). For Fusion, go to Virtual Machine > Settings > Print. Look for virtual printing or Thinprint components
    Affected if Virtual printing is enabled in any guest VM configuration

The host is affected if it runs vulnerable VMware Workstation (15.0.0 to <15.5.2) or Fusion (11.0.0 to <11.5.2) AND any Linux guest VM has virtual printing enabled.

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.

From vendor data
Upgrade available Upgrade to 11.5.2 / 15.5.2 or later
Fixed in 11.5.215.5.2
Interim mitigation

Apply VMware Workstation update 15.5.2 or later, and Fusion 11.5.2 or later to the host system. Alternatively, disable virtual printing in the guest VM settings as a workaround until patching is complete.

Fix this in Fusion Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-3948 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-3948 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