CVE-2025-23119
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 Neutralization of Escape Sequences vulnerability could allow an Authentication Bypass with a Remote Code Execution (RCE) by a malicious actor with access to UniFi Protect Cameras adjacent 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 format string/escape sequence injection vulnerability in UniFi Protect Camera firmware allows an attacker on the adjacent network to bypass authentication mechanisms and execute arbitrary code. The vulnerability stems from improper sanitization of input sequences, enabling both credential bypass and remote code execution.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:A/AC:H/PR:N/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 cameras in your environmentInventory all network devices and identify those running UniFi Protect firmware. Check your UniFi Protect controller or network management console for connected cameras.Affected if UniFi Protect cameras are present on the network
-
Check camera firmware versionAccess each camera through the UniFi Protect controller or directly via SSH/RTSP and retrieve the firmware version. Compare against any released patch versions from Ubiquiti.Affected if Camera firmware is older than the patched version released by Ubiquiti for this CVE
-
Verify network adjacency exposureExamine your network topology to determine whether untrusted or guest network segments can reach the camera management interface (typically ports 443, 8080, or the UniFi Protect application port). Check VLAN configuration and ACLs.Affected if Cameras are accessible from network segments containing untrusted or adjacent devices
-
Check management interface accessibilityFrom a host on an adjacent or untrusted network segment, attempt to reach the camera's management IP or the UniFi Protect controller. Verify if authentication can be bypassed through the format string vulnerability.Affected if Management interface responds to requests from adjacent network segments without proper network isolation
-
Review authentication mechanism configurationInspect the UniFi Protect authentication settings and verify whether the format string vulnerability can be triggered through login endpoints or camera communication channels.Affected if Authentication is handled by the affected firmware without additional compensating controls
Your environment is affected if UniFi Protect cameras run vulnerable firmware AND are accessible from adjacent network segments where untrusted devices reside.
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 dataIsolate camera networks from untrusted segments, implement strict network access controls, and apply vendor firmware updates when released. Restrict adjacency to trusted devices only.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23119 — 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-23119 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