dbcve.org
DesktopApplication · Ui

CVE-2023-28124

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
Improper usage of symmetric encryption in UI Desktop for Windows (Version 0.59.1.71 and earlier) could allow users with access to UI Desktop configuration files to decrypt their content.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

UI Desktop for Windows versions 0.59.1.71 and earlier uses symmetric encryption improperly in its configuration files, allowing users with access to those files to decrypt their contents. This indicates the encryption key or algorithm is exposed or inadequately protected, enabling plaintext recovery of sensitive configuration data.

MitigationUpgrade UI Desktop for Windows to version 0.62.3 or later. If immediate patching is not possible, restrict access to configuration files and monitor for unauthorized access.

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 if UI Desktop for Windows is installed
    Look for UI Desktop installation in typical Windows locations: C:\Program Files\UI\ or C:\Program Files (x86)\UI\, or check for the application in Add/Remove Programs. Also check the user's AppData folder (e.g., %APPDATA%\UI\) for application data.
    Affected if UI Desktop for Windows is found installed on the system
  2. Determine the installed version of UI Desktop
    Locate the main executable (typically named UI.exe or similar) and right-click to view Properties, then check the Details tab for the File Version. Alternatively, check the application's About or Help section within the GUI.
    Affected if The version number is less than 0.62.3.0 (versions 0.59.1.71 and earlier are vulnerable)
  3. Locate configuration files used by UI Desktop
    Search for configuration files in the installation directory and in %APPDATA%\UI\ or %LOCALAPPDATA%\UI\. Common config file extensions include .json, .xml, .ini, .conf, or .config.
    Affected if Configuration files exist and contain encrypted or obfuscated data fields that appear to use symmetric encryption
  4. Inspect configuration files for sensitive data exposure
    Open the configuration files in a text editor and look for encrypted-looking strings (typically Base64-encoded or hex values) that could be decrypted. Check if sensitive information like credentials, API keys, or tokens are stored in these files.
    Affected if Sensitive configuration data is stored in encrypted format that could potentially be decrypted without proper key protection

A user is affected if UI Desktop for Windows is installed with a version lower than 0.62.3.0 and contains sensitive data in its configuration files.

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. If immediate patching is not possible, restrict access to configuration files and monitor for unauthorized access.

Recommended fix High confidence

Version 0.62.3 or later

  1. 1. Check the current version of UI Desktop for Windows by opening the application and navigating to Help > About or checking the system tray/control panel.
  2. 2. If the version is below 0.62.3.0, download UI Desktop version 0.62.3 or later from the official UI source (community.ui.com or official download portal).
  3. 3. Close the running UI Desktop application if currently open.
  4. 4. Run the downloaded installer and follow the on-screen prompts to upgrade the application.
  5. 5. After installation completes, verify the new version by checking Help > About to confirm the upgrade was successful.

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

Fix this in Desktop Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-28124 — 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-28124 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