CVE-2025-23115
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 · uneditedA Use After Free vulnerability on UniFi Protect Cameras could allow a Remote Code Execution (RCE) by a malicious actor with access to UniFi Protect Cameras management network.
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 confidenceA Use After Free vulnerability in UniFi Protect Cameras allows remote code execution by an attacker with access to the camera management network. The memory corruption flaw can be exploited to achieve arbitrary code execution on affected camera devices.
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
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify UniFi Protect cameras in your environmentCheck your UniFi Protect controller dashboard or network inventory for camera devices. Look for devices with names containing 'UVC' or 'G5' etc. that are part of the UniFi Protect system.Affected if UniFi Protect cameras are present in the environment
-
Determine camera firmware versionIn the UniFi Protect controller, select each camera and view the device details. Note the firmware version displayed. Alternatively, access the camera web interface and check the firmware version in system settings.Affected if Camera firmware version is below the version that Ubiquiti has patched for CVE-2025-23115 (check Ubiquiti's security advisory for specific version numbers)
-
Verify camera management network exposureReview your firewall rules and network configuration. Determine if the camera management interface (typically ports 7443, 8080, or the UniFi Protect controller port) is accessible from networks outside your trusted internal network. Check if cameras are on an isolated VLAN with no direct internet access.Affected if Camera management interface is accessible from untrusted or external networks
-
Check for signs of exploitationReview camera logs for unexpected processes, crashes, or memory errors. Look for unfamiliar firmware changes or configuration modifications. Monitor network traffic for suspicious patterns targeting camera ports.Affected if Logs show memory corruption errors, unexpected code execution, or unauthorized configuration changes
You are affected if you have UniFi Protect cameras running firmware versions before the patched release AND your camera management network is accessible to attackers.
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 dataRestrict network access to the UniFi Protect management interface to trusted networks only and apply vendor firmware updates when released.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23115 — 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-23115 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