dbcve.org
Unifi OsOperating system · Ui

CVE-2023-31997

CRITICAL · 9.0 CVSS v3.1 Published 2023-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/100
Remediation priority · Urgent
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
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.

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

UniFi OS 3.1 contains a misconfiguration on Cloud Key Gen2 and Cloud Key Gen2 Plus devices that exposes the internal MongoDB database to local network users. This allows any user on the same network to directly access the database containing sensitive network configuration data, potentially enabling data exfiltration or unauthorized modification of network settings.

MitigationApply the appropriate UniFi OS firmware update that addresses this misconfiguration, or restrict MongoDB network access through firewall rules to prevent local network connections.

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 OsOperating system
Affected:= 3.1

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

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

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. Confirm device is Cloud Key Gen2 or Gen2 Plus
    Check the physical device model or access the UniFi OS dashboard to identify the hardware model
    Affected if Device is a Cloud Key Gen2 or Cloud Key Gen2 Plus running UniFi OS 3.1
  2. Verify UniFi OS version
    Access the UniFi OS dashboard or check via SSH with 'unifi-os version' command
    Affected if UniFi OS version is exactly 3.1 (not a later patched version)
  3. Check MongoDB network binding
    Run 'netstat -tlnp | grep 27117' or 'ss -tlnp | grep 27117' via SSH to see which interfaces MongoDB is listening on
    Affected if MongoDB is bound to 0.0.0.0 or a non-loopback IP address instead of only 127.0.0.1
  4. Test MongoDB port accessibility from LAN
    From a device on the same network, run 'nc -zv <cloudkey-ip> 27117' or use nmap to check if port 27117 is reachable
    Affected if Port 27117 on the Cloud Key is accessible from other devices on the local network

A user is affected if they are running UniFi OS 3.1 on a Cloud Key Gen2 or Gen2 Plus device where MongoDB is bound to a network-accessible interface and accepting connections from the local network.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the appropriate UniFi OS firmware update that addresses this misconfiguration, or restrict MongoDB network access through firewall rules to prevent local network connections.

Recommended fix Moderate confidence

Upgrade to the latest available UniFi OS version (later than 3.1) that contains the security fix

  1. 1. Identify the current UniFi OS version running on the affected Cloud Key Gen2 or Cloud Key Gen2 Plus device
  2. 2. Access the UniFi OS console through the web interface or SSH
  3. 3. Navigate to the system settings or check for updates within the UniFi OS dashboard
  4. 4. Apply the latest UniFi OS update available from Ubiquiti
  5. 5. After updating, verify the MongoDB service is no longer exposed to local network users by reviewing network access controls
Caveat Standard firmware upgrade risk applies - ensure backups of configuration are available before performing the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Unifi Os Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-31997 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2023-31997 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