Horizon DaasApplication · VMware
CVE-2018-6960
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 Horizon DaaS (7.x before 8.0.0) contains a broken authentication vulnerability that may allow an attacker to bypass two-factor authentication. Note: In order to exploit this issue, an attacker must have a legitimate account on Horizon DaaS.
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 Horizon DaaS versions 7.x before 8.0.0 contain a broken authentication vulnerability that allows attackers with legitimate accounts to bypass two-factor authentication. The specific mechanism of the bypass is not detailed, but the vulnerability is classified as a broken authentication flaw affecting the 2FA implementation.
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
Horizon DaasApplication
>= 7.0.0, < 8.0.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/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 Horizon DaaS is installedCheck for the presence of VMware Horizon DaaS components on the system, typically found in the installation directory or via system inventory toolsAffected if The product is present on the system
-
Determine installed version of VMware Horizon DaaSAccess the VMware Horizon DaaS admin console or use command-line tools to retrieve the product version (for example: look at the about section in the management interface or check version files in the installation directory)Affected if The installed version is 7.x (7.0.0 or higher) but lower than 8.0.0
-
Check if two-factor authentication is configuredIn the Horizon DaaS admin console, navigate to the authentication or user settings to see if 2FA is enabled for user accounts or tenant configurationsAffected if Two-factor authentication is enabled and the version is in the affected range (>=7.0.0, <8.0.0)
-
Verify authentication configuration for tenant accountsReview the tenant or user authentication settings in the Horizon DaaS management interface to confirm 2FA enforcement policies are in placeAffected if 2FA enforcement is active and the version falls within the vulnerable range
A system is affected if VMware Horizon DaaS version 7.0.0 or higher but below 8.0.0 is installed and two-factor authentication is enabled for user accounts.
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 data8.0.0
Upgrade VMware Horizon DaaS to version 8.0.0 or later to remediate the two-factor authentication bypass vulnerability.
Fix this in Horizon Daas
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6960 — 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-6960 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