# CVE-2020-27888: Information disclosure in n/a

> Cached credentials persist on Ubiquiti UniFi access points after disconnection, potentially allowing unauthorized network access.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 27 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fc89-33h9-mh65

## What is CVE-2020-27888?

CVE-2020-27888 is a high-severity vulnerability in n/a, published on 27 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on Ubiquiti UniFi Meshing Access Point UAP-AC-M 4.3.21.11325 and UniFi Controller 6.0.28 devices. Cached credentials are not erased from an access point returning wirelessly from a disconnected state. This may provide unintended network access.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-459 (Incomplete Cleanup)

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

It affects 2 products.


Products: Ui Unifi Controller Firmware, Ui Unifi Meshing Access Point Firmware.

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

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

## Is CVE-2020-27888 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-27888 is a high-severity vulnerability in n/a, published on 27 Oct 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-27888 in the wild and no public exploit code.

Affected product: n/a. 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-27888/ (Markdown: https://insights.sbomify.com/CVE-2020-27888/index.md)
```

## Sources

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

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