# CVE-2020-8148: Auth bypass in UniFi Cloud Key Gen2

> An attacker can modify the device hostname via a malicious API request due to improper authentication, affecting UniFi Cloud Key Gen2 devices.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8w47-824w-pr9m

## What is CVE-2020-8148?

CVE-2020-8148 is a medium-severity authentication bypass vulnerability in UniFi Cloud Key Gen2, published on 13 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

UniFi Cloud Key firmware < 1.1.6 contains a vulnerability that enables an attacker being able to change a device hostname by sending a malicious API request. This affects Cloud Key gen2 and Cloud Key gen2 Plus.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2020-8148?

It affects 2 products.


Products: Ui Cloud Key Gen2, Ui Cloud Key Gen2 Plus.

## How do I fix CVE-2020-8148?

No fix has been published for CVE-2020-8148 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-8148 being exploited?

There is no known exploitation of CVE-2020-8148 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-8148 and fix it if it is affected.

What it is: CVE-2020-8148 is a medium-severity authentication bypass vulnerability in UniFi Cloud Key Gen2, published on 13 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-8148 in the wild and no public exploit code.

Affected product: UniFi Cloud Key Gen2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-8148/ (Markdown: https://insights.sbomify.com/CVE-2020-8148/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-8148
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-8148
- OSV: https://osv.dev/vulnerability/CVE-2020-8148

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-8148/
Summaries are generated and may contain mistakes; the official description above is the record.