LiveActive security incident?Get immediate response
CVE Record

CVE-2020-8267: A security issue was found in UniFi Protect controller v1.14.10 and earlier.The authentication in the UniFi...

A security issue was found in UniFi Protect controller v1.14.10 and earlier.The authentication in the UniFi Protect controller API was using “x-token” improperly, allowing attackers to use the API to send authenticated messages without a valid token.This vulnerability was fixed in UniFi Protect v1.14.11 and newer.This issue does not impact UniFi Cloud Key Gen 2 plus.This issue does not impact UDM-Pro customers with UniFi Protect stopped.Affected Products:UDM-Pro firmware 1.7.2 and earlier.UNVR firmware 1.3.12 and earlier.Mitigation:Update UniFi Protect to v1.14.11 or newer version; the UniFi Protect controller can be updated through your UniFi OS settings.Alternatively, you can update UNVR and UDM-Pro to:- UNVR firmware to 1.3.15 or newer.- UDM-Pro firmware to 1.8.0 or newer.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-8267 is an authentication flaw in UniFi Protect. Affected controllers could accept API messages as authenticated even without a valid token. For organizations using UniFi Protect for physical security video operations, this creates unauthorized control-plane risk. Ubiquiti says the issue is fixed in UniFi Protect 1.14.11 and newer.

Executive priority

Patch promptly where UniFi Protect supports business-critical surveillance or site security. Escalate priority if the controller API is reachable beyond trusted administrative networks. The absence of KEV evidence lowers emergency pressure, but authentication bypass on security infrastructure warrants timely remediation.

Technical view

UniFi Protect controller 1.14.10 and earlier improperly used the API x-token authentication mechanism, allowing authenticated API messages without a valid token. The CVE maps to CWE-287. Affected platforms listed are UDM-Pro firmware 1.7.2 and earlier, and UNVR firmware 1.3.12 and earlier.

Likely exposure

Exposure is limited to environments running affected UniFi Protect versions on UDM-Pro or UNVR. UniFi Cloud Key Gen 2 Plus is stated as not impacted. UDM-Pro customers with UniFi Protect stopped are also stated as not impacted.

Exploitation context

The provided sources do not report active exploitation, public exploit use, or KEV listing. They only describe the authentication weakness and affected versions. Risk depends on whether the UniFi Protect controller API is reachable by an attacker.

Researcher notes

Source detail is sparse: no CVSS vector, no endpoint specifics, and no exploit preconditions beyond improper x-token handling. Avoid assuming device takeover or data exposure without further vendor evidence. Validation should focus on exact product, firmware, controller version, and whether Protect is running.

Mitigation direction

  • Update UniFi Protect to version 1.14.11 or newer through UniFi OS settings.
  • Alternatively update UNVR firmware to 1.3.15 or newer.
  • Alternatively update UDM-Pro firmware to 1.8.0 or newer.
  • Confirm UniFi Protect is stopped on UDM-Pro systems where it is not used.
  • Check current Ubiquiti guidance before changing production security systems.

Validation and detection

  • Inventory UDM-Pro and UNVR devices running UniFi Protect.
  • Verify UniFi Protect controller version is 1.14.11 or newer.
  • Verify UNVR firmware is 1.3.15 or newer where applicable.
  • Verify UDM-Pro firmware is 1.8.0 or newer where applicable.
  • Confirm Cloud Key Gen 2 Plus assets are not misclassified as affected.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-287: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-8267 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aUniFi ProtectUniFi Protect v1.14.10 and earlier not fixedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-287 · source CWE mapping

Improper Authentication

Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.