dbcve.org
DesktopApplication · Ui

CVE-2023-28123

MEDIUM · 5.5 CVSS v3.1 Published 2023-04-19
Fix available
A fix is available. Upgrade to 0.62.3.0 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
A permission misconfiguration in UI Desktop for Windows (Version 0.59.1.71 and earlier) could allow an user to hijack VPN credentials while UID VPN is starting.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 · moderate confidence

A permission misconfiguration in UI Desktop for Windows (versions 0.59.1.71 and earlier) allows a local user to hijack VPN credentials during the UID VPN startup process, likely through improper file or service permission settings that grant unauthorized access to sensitive credential storage.

MitigationUpgrade UI Desktop for Windows to version 0.62.3 or later to remediate the permission misconfiguration that enables credential hijacking.

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
DesktopApplication
Affected:< 0.62.3.0

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed UI Desktop version
    Locate the UI Desktop application on the Windows system and retrieve its version number (typically via Add/Remove Programs, the application's About dialog, or checking file properties of the main executable)
    Affected if The installed version is earlier than 0.62.3.0 (e.g., 0.59.1.71 or earlier)
  2. Identify UID VPN service or process
    Look for processes or services related to UID VPN running on the system (check Task Manager, Services console, or command line tools like tasklist/sc query)
    Affected if The UID VPN service or component is installed and running on the system
  3. Locate VPN credential storage
    Search for files or directories that store VPN credentials, typically in application data folders (e.g., %APPDATA%, %PROGRAMDATA%, or within the UI Desktop installation directory) related to VPN configuration or credentials
    Affected if VPN credential files exist on the system in accessible locations
  4. Inspect file permissions on credential storage
    Use Windows icacls or Explorer Security tab to examine the Access Control List (ACL) on identified VPN credential files or folders, checking if unprivileged users have Write or Modify permissions
    Affected if Users without administrative privileges can modify or replace credential files due to overly permissive ACLs
  5. Check service configuration permissions
    Review the permissions on the UID VPN Windows service (via services.msc or sc qc) to determine if non-admin users can alter service parameters or executable paths
    Affected if The service allows modification by non-privileged accounts

A user is affected if UI Desktop for Windows version is below 0.62.3.0 AND the UID VPN component is installed with improperly secured credential files or service configuration accessible to local non-admin users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 0.62.3.0 or later
Fixed in 0.62.3.0
Interim mitigation

Upgrade UI Desktop for Windows to version 0.62.3 or later to remediate the permission misconfiguration that enables credential hijacking.

Recommended fix High confidence

Version 0.62.3 or later

  1. 1. Open UI Desktop for Windows on the affected machine
  2. 2. Navigate to the application settings or help section
  3. 3. Check the current installed version number
  4. 4. If the version is below 0.62.3, download the latest version from the official UI Desktop download source
  5. 5. Run the installer to upgrade to version 0.62.3 or later
  6. 6. Restart the UI Desktop application
  7. 7. Verify the installed version shows 0.62.3 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Desktop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-28123 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-28123 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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