# CVE-2021-22882: Denial of service in UniFi Protect

> Attackers can crash the UniFi Protect controller by using spoofed cameras, causing a denial of service for security monitoring systems.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Feb 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-9727-xj59-f5g3

## What is CVE-2021-22882?

CVE-2021-22882 is a high-severity denial of service vulnerability in UniFi Protect, published on 23 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

UniFi Protect before v1.17.1 allows an attacker to use spoofed cameras to perform a denial-of-service attack that may cause the UniFi Protect controller to crash.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2021-22882?

It affects 1 product.


Products: Ui Unifi Protect Controller.

## How do I fix CVE-2021-22882?

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

## Is CVE-2021-22882 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-22882 and fix it if it is affected.

What it is: CVE-2021-22882 is a high-severity denial of service vulnerability in UniFi Protect, published on 23 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-22882 in the wild and no public exploit code.

Affected product: UniFi Protect. 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-2021-22882/ (Markdown: https://insights.sbomify.com/CVE-2021-22882/index.md)
```

## Sources

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

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