Unifi VideoApplication · Ui

CVE-2020-8145

MEDIUM · 6.5 CVSS v3.1 Published 2020-04-01
Fix available
A fix is available. Upgrade to after 3.9.3 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
The UniFi Video Server (Windows) web interface configuration restore functionality at the “backup” and “wizard” endpoints does not implement sufficient privilege checks. Low privileged users, belonging to the PUBLIC_GROUP or CUSTOM_GROUP groups, can access these endpoints and overwrite the current application configuration. This can be abused for various purposes, including adding new administrative users. Affected Products: UniFi Video Controller v3.9.3 (for Windows 7/8/10 x64) and prior. Fixed in UniFi Video Controller v3.9.6 and newer.

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

The UniFi Video Server (Windows) web interface contains insufficient authorization checks at the backup and wizard endpoints used for configuration restore. Users with low privileges assigned to PUBLIC_GROUP or CUSTOM_GROUP can directly access these endpoints and overwrite the application configuration, enabling them to add new administrative users and gain full system access.

MitigationUpgrade UniFi Video Controller to version 3.9.6 or newer. Additionally, audit and restrict user group assignments to ensure low-privileged users cannot access sensitive configuration endpoints.

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
Unifi VideoApplication
Affected:<= 3.9.3

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed UniFi Video version
    Open the UniFi Video Controller web interface and navigate to Settings > System, or check the Windows Programs and Features list for 'UniFi Video' version. Alternatively, check the install directory for a version file.
    Affected if The installed version is 3.9.3 or lower (any version <= 3.9.3)
  2. Confirm web interface is accessible
    Verify the UniFi Video web interface (default ports 7080, 7443 or 80/443 if configured) is reachable on the network.
    Affected if The web interface is exposed and reachable
  3. Identify user group assignments
    Log into the UniFi Video web interface as an administrator and navigate to Users or Groups management. Review all user accounts and note their assigned group membership, specifically looking for PUBLIC_GROUP or CUSTOM_GROUP assignments.
    Affected if Any user account is assigned to PUBLIC_GROUP or CUSTOM_GROUP (low-privilege groups)
  4. Test backup endpoint access
    Using a low-privilege user account (assigned to PUBLIC_GROUP or CUSTOM_GROUP), attempt to access the backup/restore endpoint directly via browser or curl: http(s)://<server>:<port>/api/backup or similar configuration restore URLs.
    Affected if A low-privilege user can access and trigger configuration restore functions without admin authentication

If the UniFi Video version is 3.9.3 or lower AND low-privilege users exist in PUBLIC_GROUP or CUSTOM_GROUP, the environment is affected by this authorization bypass vulnerability.

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 a release after 3.9.3
Interim mitigation

Upgrade UniFi Video Controller to version 3.9.6 or newer. Additionally, audit and restrict user group assignments to ensure low-privileged users cannot access sensitive configuration endpoints.

Fix this in Unifi Video Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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