Remote Desktop ManagerApplication · Devolutions

CVE-2025-1635

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-13
Fix available
A fix is available. Upgrade to 2024.3.31.0 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
Exposure of sensitive information in hub data source export feature in Devolutions Remote Desktop Manager 2024.3.29 and earlier on Windows allows a user exporting a hub data source to include his authenticated session in the export due to faulty business logic.

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

In Devolutions Remote Desktop Manager 2024.3.29 and earlier on Windows, the hub data source export feature includes authenticated session information in the exported data due to faulty business logic, exposing sensitive session credentials to unauthorized parties who receive the export.

MitigationUpgrade to Remote Desktop Manager version 2024.3.30 or later. Review and revoke any exported session credentials that may have been exposed prior to patching.

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

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 installed Remote Desktop Manager version
    Open Remote Desktop Manager, go to Help > About, or check Programs and Features for the installed version number
    Affected if Version is earlier than 2024.3.31.0
  2. Identify hub data source configuration
    In Remote Desktop Manager, navigate to Data Sources or Connections settings to see if a Hub data source type is configured and active
    Affected if A Hub data source is configured and connected
  3. Review recent export activity
    Check the application logs or recent file modifications in the export destination folder for .rdm, .xml, or .json export files originating from Hub data sources
    Affected if Hub data source exports were performed and contain session data
  4. Inspect exported file contents
    Open a recent Hub export file in a text editor and search for credential-related fields such as passwords, tokens, or session keys within connection entries
    Affected if The exported file contains plaintext or encoded session credentials

You are affected if Remote Desktop Manager version is below 2024.3.31.0 AND you have exported data from a Hub data source, as the export would include authenticated session credentials.

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

Upgrade to Remote Desktop Manager version 2024.3.30 or later. Review and revoke any exported session credentials that may have been exposed prior to patching.

Recommended fix High confidence

2024.3.31.0 or later

  1. 1. Open Remote Desktop Manager application
  2. 2. Navigate to Help > Check for Updates
  3. 3. If an update is available, download and install version 2024.3.31.0 or later
  4. 4. Alternatively, download the latest version from the official Devolutions website: https://devolutions.net/remote-desktop-manager/download
  5. 5. After updating, verify the version by checking Help > About to confirm version 2024.3.31.0 or higher is installed
  6. 6. When exporting hub data sources after update, verify that authenticated session data is no longer included in exports by design

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,280
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,248.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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