CVE-2023-28122
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 (LPE) vulnerability in UI Desktop for Windows (Version 0.59.1.71 and earlier) allows a malicious actor with local access to a Windows device running said application to submit arbitrary commands as SYSTEM.This vulnerability is fixed in Version 0.62.3 and later.
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 · high confidenceUI Desktop for Windows versions 0.59.1.71 and earlier contains a local privilege escalation vulnerability that allows an attacker with local access to the Windows device to execute arbitrary commands with SYSTEM-level privileges. The flaw appears to involve improper privilege management within the application that can be exploited by a malicious local user.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.62.3.0CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 if UI Desktop for Windows is installedCheck the installed programs list via Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed applications and versionsAffected if UI Desktop for Windows appears in the installed programs list
-
Determine the installed version of UI DesktopLocate the exact version number in the Programs and Features list, or check the application's About/Properties section if accessible, or look for UI Desktop in Add/Remove Programs which typically displays the versionAffected if The displayed version is 0.59.1.71 or earlier, or any version less than 0.62.3.0
-
Verify the vulnerability is present based on versionCompare your installed UI Desktop version against the affected range: versions prior to 0.62.3.0 are vulnerableAffected if The installed version is below 0.62.3.0 (for example: 0.59.1.71, 0.60.0.0, 0.61.0.0, etc.)
A user is affected if UI Desktop for Windows is installed and the installed version is less than 0.62.3.0, as only versions below this threshold contain the improper privilege management flaw.
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 · scoped0.62.3.0
Upgrade UI Desktop for Windows to version 0.62.3 or later to remediate this vulnerability.
Version 0.62.3 or later
- Check current UniFi Desktop version by opening the application and navigating to Settings > About
- Download UniFi Desktop version 0.62.3 or later from the official Ubiquiti downloads page (ui.com/downloads)
- Close the UniFi Desktop application completely before upgrading
- Run the installer with administrator privileges and follow the prompts to complete the upgrade
- After installation, verify the version shows 0.62.3.0 or later in Settings > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28122 — 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-2023-28122 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