dbcve.org
Unifi Network ApplicationApplication · Ui

CVE-2023-41721

MEDIUM · 5.3 CVSS v3.1 Published 2023-10-25
Fix available
A fix is available. Upgrade to after 7.5.176 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Instances of UniFi Network Application that (i) are run on a UniFi Gateway Console, and (ii) are versions 7.5.176. and earlier, implement device adoption with improper access control logic, creating a risk of access to device configuration information by a malicious actor with preexisting access to the network. Affected Products: UDM UDM-PRO UDM-SE UDR UDW Mitigation: Update UniFi Network to Version 7.5.187 or later.

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

Improper access control in UniFi Network Application's device adoption logic allows a malicious actor with preexisting network access to obtain device configuration information. The vulnerability affects UniFi Gateway Consoles running versions 7.5.176 and earlier, where the adoption process fails to properly validate authorization before exposing configuration data.

MitigationUpdate UniFi Network Application to version 7.5.187 or later on all affected UniFi Gateway Console devices (UDM, UDM-PRO, UDM-SE, UDR, UDW) to remediate the improper access control vulnerability.

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 Network ApplicationApplication
Affected:<= 7.5.176

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

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. Identify UniFi Network Application installation
    Locate the UniFi Network Application installation - this may be running on a UniFi Gateway Console (UDM, UDM-PRO, UDM-SE, UDR, UDW) or as a standalone controller on a dedicated server. Check system processes or services for the UniFi controller application.
    Affected if UniFi Network Application is installed and running on any supported platform.
  2. Check installed UniFi Network Application version
    Access the UniFi Network Application dashboard and navigate to Settings > System > About, or use the command line interface (via SSH to the controller) and run: 'unifi-os version' on Gateway Consoles, or check the application package version on standalone controllers.
    Affected if The installed version is 7.5.176 or earlier.
  3. Verify device adoption feature accessibility
    Check if the device adoption endpoints are network-accessible from untrusted network segments. Review firewall rules and network ACLs that control access to ports used by the adoption service (typically ports 8080, 8443, or the inform port 8081).
    Affected if Device adoption ports are accessible from network segments without proper authentication controls.
  4. Confirm unauthorized device configuration exposure risk
    Test whether unauthenticated or improperly authenticated requests to the adoption endpoints return device configuration data. This requires security assessment tools or understanding of the UniFi adoption API endpoints.
    Affected if Adoption logic returns configuration data without verifying authorization credentials.

A system is affected if it runs UniFi Network Application version 7.5.176 or earlier AND has device adoption functionality accessible from the network, allowing unauthorized retrieval of device configuration information.

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
Upgrade available Upgrade to a release after 7.5.176
Interim mitigation

Update UniFi Network Application to version 7.5.187 or later on all affected UniFi Gateway Console devices (UDM, UDM-PRO, UDM-SE, UDR, UDW) to remediate the improper access control vulnerability.

Recommended fix High confidence

UniFi Network Application version 7.5.187 or later

  1. Access the UniFi Network Application controller interface
  2. Navigate to the settings or system section
  3. Check the current UniFi Network Application version (should be <= 7.5.176 if affected)
  4. Apply the firmware/software update to UniFi Network Application version 7.5.187 or later
  5. Verify the update was successful and the version is now 7.5.187 or newer

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

Fix this in Unifi Network Application Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-41721 — 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-41721 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