FusionApplication · VMware
CVE-2018-6962
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 Fusion (10.x before 10.1.2) contains a signature bypass vulnerability which may lead to a local privilege escalation.
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 · moderate confidenceVMware Fusion 10.x before 10.1.2 contains a signature bypass vulnerability that allows local attackers to bypass code signing verification mechanisms, potentially leading to privilege escalation from a standard user account to elevated (root) privileges on the host system.
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
>= 10.0, < 10.1.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/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 checksWork through these to decide whether this CVE applies to you.
-
Verify VMware Fusion is installedCheck if /Applications/VMware Fusion.app exists, or run: ls /Applications/ | grep -i fusionAffected if The application directory exists on the system
-
Determine installed VMware Fusion versionRun: /Applications/VMware\ Fusion.app/Contents/MacOS/vmware-installer -l 2>/dev/null || defaults read /Applications/VMware\ Fusion.app/Contents/Info.plist CFBundleVersionAffected if Command returns a version number
-
Compare version to affected rangeCompare the extracted version against the vulnerable range: 10.0.0 through 10.1.1 (all versions >= 10.0.0 and < 10.1.2 are affected)Affected if Version is 10.0.x, 10.1.0, or 10.1.1 (any version >= 10.0.0 and < 10.1.2)
-
Confirm the code signing bypass is exploitableThis vulnerability requires a standard user account on the macOS host to place a malicious executable in a location where Fusion loads code. The flaw allows unsigned code to execute with elevated privileges.Affected if A standard (non-admin) user account exists on the host system and VMware Fusion is installed
User is affected if VMware Fusion version is 10.0.0 through 10.1.1 (any version >= 10.0.0 and < 10.1.2) and the host has standard user accounts that could be exploited for privilege escalation.
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.
From vendor data10.1.2
Upgrade VMware Fusion to version 10.1.2 or later to obtain the patched version that addresses the signature validation bypass.
Fix this in Fusion
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6962 — 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-2018-6962 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