CVE-2024-42028
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 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.
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 local privilege escalation vulnerability in UniFi Network Application versions 8.4.62 and earlier allows a malicious local OS user to execute high-privilege actions on the UniFi Network Server by exploiting insufficient access controls or privilege validation within the application.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 Network Application versionAccess the UniFi Network Application web interface and navigate to Settings > System, or check the version via command line if running on Linux (dpkg -l unifi or rpm -qa unifi)Affected if The displayed version is 8.4.62 or earlier
-
Compare version against affected rangeLocate the exact version number from the web UI or system package manager output and compare numerically to 8.4.62Affected if Version is less than or equal to 8.4.62
-
Verify local user access exists on the host systemCheck if the operating system hosting UniFi Network Application has multiple local user accounts (use 'whoami' and check system user accounts)Affected if The host system permits multiple local OS users to access the server where UniFi Network Application runs
You are affected if the UniFi Network Application installed on your system is version 8.4.62 or earlier and the server hosting it allows local OS user access.
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.
dbcve · scopedUpgrade UniFi Network Application to a version newer than 8.4.62; limit local OS access to trusted personnel and apply least-privilege principles to system accounts.
UniFi Network Application 8.4.63 or later (latest stable release)
- 1. Back up the UniFi Network Application configuration and database before any upgrade.
- 2. Access the UniFi Network Server console via SSH or console access.
- 3. For self-hosted UniFi Network deployments, update the UniFi Network Application to the latest stable version using the appropriate package manager or installer.
- 4. Verify the upgrade completed successfully by checking the application version in the UniFi Network web interface.
- 5. Confirm normal operation by logging into the UniFi Network web interface and verifying connected devices are reporting correctly.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-42028 — 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-2024-42028 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