dbcve.org
WorkspaceApplication · Devolutions

CVE-2023-2257

HIGH · 7.8 CVSS v3.1 Published 2023-04-24
Fix available
A fix is available. Upgrade to 2023.1.1.4 or later.
See remediation →
80/100
Remediation priority · High
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
Authentication Bypass in Hub Business integration in Devolutions Workspace Desktop 2023.1.1.3 and earlier on Windows and macOS allows an attacker with access to the user interface to unlock a Hub Business space without being prompted to enter the password via an unimplemented "Force Login" security feature. This vulnerability occurs only if "Force Login" feature is enabled on the Hub Business instance and that an attacker has access to a locked Workspace desktop application configured with a Hub Business space.

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 confidence

The Force Login security feature in Devolutions Workspace Desktop 2023.1.1.3 and earlier was not properly implemented, allowing an authenticated user with UI access to bypass the password prompt when unlocking a Hub Business space. This occurs specifically when the Force Login feature is enabled on the Hub Business instance, but the desktop application fails to enforce the password requirement.

MitigationUpgrade Devolutions Workspace Desktop to version 2023.1.2 or later where the Force Login feature is properly implemented. Until then, ensure physical access controls and limit desktop application access to trusted users only.

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
WorkspaceApplication
Affected:< 2023.1.1.4

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
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 checks

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

  1. Check Devolutions Workspace Desktop version
    Open Devolutions Workspace Desktop, go to Help > About or check the application version in the system-installed programs list. Compare the version number to the affected range: 2023.1.1.3 and earlier.
    Affected if The installed version is 2023.1.1.3 or earlier.
  2. Confirm Hub Business connection
    In Devolutions Workspace Desktop, verify you have at least one Hub Business connection configured and accessible.
    Affected if A Hub Business connection is configured and available in the application.
  3. Check if Force Login is enabled on Hub Business
    Log into the Hub Business web interface or admin panel, navigate to the security or authentication settings for the workspace, and verify whether the Force Login feature is turned on.
    Affected if Force Login is enabled on the Hub Business instance.
  4. Test password bypass vulnerability
    With Force Login enabled on Hub Business, lock the workspace in the desktop application and attempt to unlock it. Observe whether the password prompt is displayed or if access is granted without requiring credentials.
    Affected if The workspace unlocks without prompting for a password when Force Login is enabled on the Hub Business instance.

A user is affected if they are running Devolutions Workspace Desktop version 2023.1.1.3 or earlier, have a Hub Business connection with Force Login enabled, and can unlock the workspace without being prompted for a password.

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 2023.1.1.4 or later
Fixed in 2023.1.1.4
Interim mitigation

Upgrade Devolutions Workspace Desktop to version 2023.1.2 or later where the Force Login feature is properly implemented. Until then, ensure physical access controls and limit desktop application access to trusted users only.

Recommended fix High confidence

2023.1.1.4

  1. Check current Devolutions Workspace Desktop version (Help > About) to confirm it is 2023.1.1.3 or earlier
  2. Download Devolutions Workspace Desktop version 2023.1.1.4 or later from the official Devolutions website
  3. Install the updated version by running the installer and following the on-screen prompts
  4. Restart the application if prompted
  5. Verify the version now shows 2023.1.1.4 or later to confirm the update was applied

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

Fix this in Workspace Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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