# CVE-2024-42028: Privilege escalation in UniFi Network Application

> A local user can escalate privileges to execute high-privilege actions on the UniFi Network Server, requiring an upgrade to mitigate.

- **Severity:** High 8.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Oct 2024
- **Updated:** 28 Oct 2024
- **Also known as:** GHSA-jhcf-hv78-23rq

## What is CVE-2024-42028?

CVE-2024-42028 is a high-severity vulnerability in Ubiquiti Inc UniFi Network Application, published on 28 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A Local privilege escalation vulnerability found in a Self-Hosted UniFi Network Server with UniFi Network Application (Version 8.4.62 and earlier) allows a malicious actor with a local operational system user to execute high privilege actions on UniFi Network Server.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2024-42028?


## How do I fix CVE-2024-42028?

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

## Is CVE-2024-42028 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-42028 and fix it if it is affected.

What it is: CVE-2024-42028 is a high-severity vulnerability in Ubiquiti Inc UniFi Network Application, published on 28 Oct 2024. 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-2024-42028 in the wild and no public exploit code.

Affected product: Ubiquiti Inc UniFi Network Application. 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-2024-42028/ (Markdown: https://insights.sbomify.com/CVE-2024-42028/index.md)
```

## Sources

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

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