CVE-2025-23118
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 · uneditedAn Improper Certificate Validation vulnerability could allow an authenticated malicious actor with access to UniFi Protect Cameras adjacent network to make unsupported changes to the camera system.
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 · moderate confidenceThis is an improper certificate validation vulnerability in UniFi Protect Cameras firmware. An authenticated attacker on the adjacent network can exploit weak or missing certificate validation to make unauthorized changes to the camera system, potentially allowing firmware tampering or man-in-the-middle attacks on camera communications.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:A/AC:H/PR:H/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Identify UniFi Protect Camera model and firmware versionAccess the UniFi Protect controller or the camera's web interface to view the device information. Look for the firmware version number listed under camera properties.Affected if The camera is running a firmware version that lacks the certificate validation fix (compare against vendor release notes for patched versions).
-
Verify network segment placement of the cameraCheck the network configuration to determine which VLAN or network segment the camera is connected to. Review switch/router configuration to confirm network boundaries.Affected if The camera is on an untrusted or adjacent network segment that allows access from non-administrator authenticated users or guest networks.
-
Confirm certificate validation is enabled for camera communicationsIn the UniFi Protect controller settings, locate the camera connection security settings. Verify that TLS/certificate validation is explicitly enabled for camera-to-controller communications.Affected if Certificate validation is disabled, set to optional, or uses a fallback to insecure connections.
-
Review camera management access controlsCheck the UniFi Protect access control settings to identify which users have administrative privileges and from which network locations those credentials can be used.Affected if Non-administrator accounts or credentials from adjacent network segments have authentication access to camera management functions.
A user is affected if their UniFi Protect Camera firmware lacks the certificate validation fix and the camera is accessible from adjacent network segments with authenticated access.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply vendor patches for UniFi Protect Cameras firmware when available. Until then, restrict network access to cameras to trusted segments only and ensure only authorized administrators have authentication credentials.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23118 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-23118 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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