# CVE-2025-23117: Security feature bypass in UniFi Protect Cameras

> An authenticated attacker on the adjacent network can bypass firmware validation to make unsupported changes to UniFi Protect Cameras.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Mar 2025
- **Updated:** 5 Mar 2025
- **Also known as:** GHSA-9fr5-pmw2-2894

## What is CVE-2025-23117?

CVE-2025-23117 is a medium-severity vulnerability in Ubiquiti Inc UniFi Protect Cameras, published on 1 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An Insufficient Firmware Update Validation vulnerability could allow an authenticated malicious actor with access to UniFi Protect Cameras adjacent network to make unsupported changes to the camera system.

Weakness: CWE-346 (Origin Validation Error)

## Which versions are affected by CVE-2025-23117?


## How do I fix CVE-2025-23117?

No fix has been published for CVE-2025-23117 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-23117 being exploited?

There is no known exploitation of CVE-2025-23117 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-23117 and fix it if it is affected.

What it is: CVE-2025-23117 is a medium-severity vulnerability in Ubiquiti Inc UniFi Protect Cameras, published on 1 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-23117 in the wild and no public exploit code.

Affected product: Ubiquiti Inc UniFi Protect Cameras. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-23117/ (Markdown: https://insights.sbomify.com/CVE-2025-23117/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-23117
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-23117
- OSV: https://osv.dev/vulnerability/CVE-2025-23117

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-23117/
Summaries are generated and may contain mistakes; the official description above is the record.