dbcve.org
Remote Desktop ManagerApplication · Devolutions

CVE-2023-1203

MEDIUM · 6.5 CVSS v3.1 Published 2023-03-10
Fix available
A fix is available. Upgrade to 2022.3.1.6 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
Improper removal of sensitive data in the entry edit feature of Hub Business submodule in Devolutions Remote Desktop Manager PowerShell Module 2022.3.1.5 and earlier allows an authenticated user to access sensitive data on entries that were edited using the affected submodule.

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

Improper removal of sensitive data in the entry edit feature of Hub Business submodule in Devolutions Remote Desktop Manager PowerShell Module allows authenticated users to access sensitive data that should have been removed when entries were edited.

MitigationUpgrade to a version newer than 2022.3.1.5 where the sensitive data removal logic has been fixed in the entry edit workflow.

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:< 2022.3.1.6

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

CVSS:3.1/AV:N/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 Remote Desktop Manager version
    Open Remote Desktop Manager and go to Help > About, or check the installed version via the Windows Programs and Features list
    Affected if The installed version is earlier than 2022.3.1.6 (or the version shown is < 2022.3.1.6)
  2. Verify PowerShell Module usage
    Check if the Remote Desktop Manager PowerShell Module (likely named 'RemoteDesktopManager.PowerShellModule' or similar) is installed by running 'Get-Module -ListAvailable' in PowerShell
    Affected if The PowerShell Module is installed and the main application version is vulnerable
  3. Confirm Hub Business submodule is in use
    Check if entries from a Hub Business vault are being managed. Look for connections or entries tagged as Hub Business type within Remote Desktop Manager
    Affected if You are using Hub Business entries (not local or other vault types)
  4. Inspect edited entries for retained sensitive data
    For any entries that were previously edited using the entry edit feature in the Hub Business submodule, examine the raw entry data or XML/JSON export to see if sensitive fields (passwords, credentials, API keys) that were supposedly removed during edit still exist
    Affected if Edited Hub Business entries contain sensitive data that should have been cleared during the edit operation

You are affected if Remote Desktop Manager version is before 2022.3.1.6 AND you use the Hub Business submodule PowerShell Module with entries that have been edited (where sensitive data may have been retained improperly).

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

Upgrade to a version newer than 2022.3.1.5 where the sensitive data removal logic has been fixed in the entry edit workflow.

Recommended fix High confidence

2022.3.1.6

  1. Identify the current version of Remote Desktop Manager PowerShell Module installed in your environment
  2. Download and install Remote Desktop Manager version 2022.3.1.6 or later from the official Devolutions website
  3. Verify the installed version after upgrade to confirm the patch was applied

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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