dbcve.org
Remote Desktop ManagerApplication · Devolutions

CVE-2022-3641

HIGH · 8.8 CVSS v3.1 Published 2022-12-12
Fix available
A fix is available. Upgrade to 2022.3.26 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Elevation of privilege in the Azure SQL Data Source in Devolutions Remote Desktop Manager 2022.3.13 to 2022.3.24 allows an authenticated user to spoof a privileged account.

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

An authenticated user can elevate their privileges by spoofing a privileged account in the Azure SQL Data Source feature of Devolutions Remote Desktop Manager versions 2022.3.13 through 2022.3.24. The vulnerability allows a lower-privileged authenticated user to impersonate higher-privileged accounts when connecting to Azure SQL data sources.

MitigationUpdate Devolutions Remote Desktop Manager to a version beyond 2022.3.24 to receive the security fix for this privilege escalation 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:>= 2022.3.13, < 2022.3.26

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

CVSS:3.1/AV:N/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 installed version of Remote Desktop Manager
    Open the application and navigate to Help > About, or check the version displayed on the application splash screen on startup. Alternatively, check the installed programs list in Windows Control Panel.
    Affected if The installed version is 2022.3.13, 2022.3.14, 2022.3.15, 2022.3.16, 2022.3.17, 2022.3.18, 2022.3.19, 2022.3.20, 2022.3.21, 2022.3.22, 2022.3.23, or 2022.3.24.
  2. Verify Azure SQL Data Source is configured
    Open the data source manager in Remote Desktop Manager and review the list of configured connections. Look for entries using Azure SQL or Microsoft Azure SQL Database as the data source type.
    Affected if Azure SQL or Microsoft Azure SQL Database data sources are configured and actively used.
  3. Identify multiple user entries in Azure SQL configuration
    In the Azure SQL data source settings, review all saved entries or user accounts that connect to the Azure SQL database. Check for entries with different permission levels (such as admin versus standard user accounts).
    Affected if Multiple user accounts with varying privilege levels are configured to connect to the same Azure SQL data source.

A user is affected if their installed version is between 2022.3.13 and 2022.3.24 inclusive, they have Azure SQL data sources configured, and there are multiple accounts with different privilege levels connected to those data sources.

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.26 or later
Fixed in 2022.3.26
Interim mitigation

Update Devolutions Remote Desktop Manager to a version beyond 2022.3.24 to receive the security fix for this privilege escalation vulnerability.

Recommended fix High confidence

2022.3.26 or later

  1. 1. Open Remote Desktop Manager application
  2. 2. Navigate to the Help menu or check for updates
  3. 3. If automatic updates are enabled, the application should prompt you to update to version 2022.3.26 or later
  4. 4. Alternatively, download the latest version (2022.3.26 or newer) from the official Devolutions website at devolutions.net
  5. 5. Run the installer and follow the on-screen instructions to complete the update
  6. 6. After updating, verify the version by going to Help > About to confirm you are running 2022.3.26 or higher
  7. 7. Test that the Azure SQL Data Source functionality works correctly with the update

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

Fix this in Remote Desktop Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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