# CVE-2023-31997: UniFi OS 3.1 introduces a misconfiguration on consoles running UniFi Network that allows users on a local network to access MongoDB.


- **Severity:** Critical 9.0 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Jun 2023
- **Updated:** 26 Nov 2024
- **Also known as:** GHSA-9chj-jjcm-3mr7

## What is CVE-2023-31997?

CVE-2023-31997 is a critical vulnerability in Ubiquiti Inc. UniFi OS, published on 30 Jun 2023. 

### Official description

UniFi OS 3.1 introduces a misconfiguration on consoles running UniFi Network that allows users on a local network to access MongoDB. Applicable Cloud Keys that are both (1) running UniFi OS 3.1 and (2) hosting the UniFi Network application. "Applicable Cloud Keys" include the following: Cloud Key Gen2 and Cloud Key Gen2 Plus.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2023-31997?

It affects 1 product.


Products: Ui Unifi Os.

## How do I fix CVE-2023-31997?

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

## Is CVE-2023-31997 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-31997 and fix it if it is affected.

What it is: CVE-2023-31997 is a critical vulnerability in Ubiquiti Inc. UniFi OS, published on 30 Jun 2023. 
Exploitation: There is no known exploitation of CVE-2023-31997 in the wild and no public exploit code.

Affected product: Ubiquiti Inc. UniFi OS. 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-2023-31997/ (Markdown: https://insights.sbomify.com/CVE-2023-31997/index.md)
```

## Sources

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

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