Remote Desktop ManagerApplication · Devolutions

CVE-2023-5765

CRITICAL · 9.8 CVSS v3.1 Published 2023-11-01
Fix available
A fix is available. Upgrade to after 2023.2.33 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 access control in the password analyzer feature in Devolutions Remote Desktop Manager 2023.2.33 and earlier on Windows allows an attacker to bypass permissions via data source switching.

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

Improper access control in the password analyzer feature of Remote Desktop Manager allows authenticated users to bypass permission checks by switching data sources, potentially exposing sensitive credentials to unauthorized users.

MitigationUpdate Devolutions Remote Desktop Manager to version 2023.2.34 or later to remediate this vulnerability.

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
Remote Desktop ManagerApplication
Affected:<= 2023.2.33

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 installed Remote Desktop Manager version
    Open the application, then go to Help > About to view the exact version number installed
    Affected if Version displayed is 2023.2.33 or any earlier version (anything <= 2023.2.33)
  2. Verify password analyzer feature is in use
    In Remote Desktop Manager, locate the password analyzer feature (typically found under Tools or Dashboard menus) and confirm whether it is configured or active
    Affected if Password analyzer feature is enabled or configured and the version is vulnerable
  3. Identify configured data sources
    In Remote Desktop Manager, view the list of configured data sources (usually in the left panel or under Data Sources menu) to see if multiple data sources are connected
    Affected if More than one data source is configured and the application version is in the affected range
  4. Review user access to data sources
    Examine the permission settings for each data source to determine if authenticated users have access to switch between different data sources
    Affected if Users have permissions to access multiple data sources and the version is vulnerable

A user is affected if Remote Desktop Manager version is 2023.2.33 or earlier, the password analyzer feature is enabled, and multiple data sources are accessible to authenticated users who could potentially switch between them to bypass permission checks.

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 a release after 2023.2.33
Interim mitigation

Update Devolutions Remote Desktop Manager to version 2023.2.34 or later to remediate this vulnerability.

Recommended fix Moderate confidence

Any version newer than 2023.2.33 (check Devolutions release notes for exact fixed version)

  1. Verify current Remote Desktop Manager version by opening the application and checking About/Help section
  2. Download the latest version of Remote Desktop Manager from the official Devolutions website (devolutions.net)
  3. Close any running instances of Remote Desktop Manager
  4. Run the installer and follow prompts to upgrade
  5. After installation, verify the new version number in the application
Caveat Review release notes for version 2023.3.x for any feature changes or migration requirements

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

Fix this in Remote Desktop Manager Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-5765 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