Remote Desktop ManagerApplication · Devolutions

CVE-2023-1202

MEDIUM · 6.5 CVSS v3.1 Published 2023-04-02
Fix available
A fix is available. Upgrade to 2023.1.10 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Permission bypass when importing or synchronizing entries in User vault in Devolutions Remote Desktop Manager 2023.1.9 and prior versions allows users with restricted rights to bypass entry permission via id collision.

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

In Devolutions Remote Desktop Manager 2023.1.9 and prior, a permission bypass vulnerability exists in the User vault import and synchronization functions. Users with restricted rights can exploit an ID collision flaw to gain access to entries they should not have permission to view or modify. The vulnerability stems from improper handling of entry IDs during import/sync operations, allowing authorization controls to be circumvented.

MitigationUpgrade to Remote Desktop Manager version 2023.1.10 or later. Until then, restrict import/sync permissions for untrusted users and monitor vault access logs for unauthorized entry 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
Remote Desktop ManagerApplication
Affected:< 2023.1.10

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 Remote Desktop Manager version
    Open the application, then go to Help > About, or inspect the Windows registry at HKLM\SOFTWARE\Devolutions\RemoteDesktopManager for the Version value, or check the properties of the installed executable.
    Affected if The installed version is earlier than 2023.1.10 (any version 2023.1.9 or prior).
  2. Verify User vault import or sync feature usage
    Check if any users have performed vault import or synchronization operations by reviewing vault access logs or asking administrators if import/sync functions have been used.
    Affected if User vault import or synchronization has been performed in the affected version range.
  3. Identify users with restricted vault permissions
    Review user accounts and their assigned vault permissions in the application, specifically looking for users who have limited or restricted access to certain entries.
    Affected if There are users with restricted rights configured in the vault.
  4. Review vault access logs for unauthorized entry access
    Examine vault audit or access logs for any instances where restricted users accessed entries outside their granted permissions, particularly around import/sync operation timestamps.
    Affected if Logs show entry access by restricted users for entries outside their assigned permissions.

You are affected if Remote Desktop Manager version is below 2023.1.10 AND users with restricted permissions have performed or received vault import/synchronization operations.

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.10 or later
Fixed in 2023.1.10
Interim mitigation

Upgrade to Remote Desktop Manager version 2023.1.10 or later. Until then, restrict import/sync permissions for untrusted users and monitor vault access logs for unauthorized entry access.

Recommended fix High confidence

2023.1.10

  1. Back up your current Remote Desktop Manager data and configuration before upgrading
  2. Download Remote Desktop Manager version 2023.1.10 or later from the official Devolutions source (devolutions.net)
  3. Install the new version following standard installation procedures
  4. Verify the installation was successful and test that restricted users can no longer bypass entry permissions via id collision during import or sync operations

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

Fix this in Remote Desktop Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,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 $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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