CVE-2025-1636
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 · uneditedExposure of sensitive information in My Personal Credentials password history component in Devolutions Remote Desktop Manager 2024.3.29 and earlier on Windows allows an authenticated user to inadvertently leak the My Personal Credentials in a shared vault via the clear history feature 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 · high confidenceIn Devolutions Remote Desktop Manager 2024.3.29 and earlier for Windows, the My Personal Credentials password history component contains faulty business logic in its clear history feature. When an authenticated user clears their password history, the feature inadvertently leaks their personal credentials into a shared vault, exposing sensitive information to other vault users.
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< 2024.3.31.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed version of Remote Desktop ManagerOpen Remote Desktop Manager, go to Help > About, or check the application version in the Windows Programs and Features list. Compare the version number to the affected range: versions prior to 2024.3.31.0 are vulnerable.Affected if The installed version is 2024.3.29 or earlier, or any version below 2024.3.31.0
-
Determine if any shared vaults are accessibleCheck the vault list in Remote Desktop Manager to see if there are any shared vaults configured. Look for vaults marked as shared or located on a network path or shared data source.Affected if The user has access to one or more shared vaults and is running a vulnerable version
-
Check for use of the clear history featureReview the application logs or audit history for any instances where the 'clear password history' or 'clear history' action was performed on personal credentials.Affected if The clear history feature was used on personal credentials while running a vulnerable version with access to shared vaults
-
Inspect shared vault entries for unexpected personal credentialsBrowse all entries in any shared vaults and look for credential entries that contain what should be personal (private) credentials. Check entry details for credentials that match your personal login data.Affected if Shared vault entries contain credentials that should be private personal credentials and were not intentionally placed there
A user is affected if they are running Remote Desktop Manager version below 2024.3.31.0, have access to shared vaults, and have used the clear history feature, potentially resulting in personal credentials appearing in shared vault entries.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2024.3.31.0
Upgrade to Remote Desktop Manager version 2024.3.30 or later. Until patched, avoid using the clear history feature on accounts that have access to shared vaults, and review shared vault entries for any inadvertently exposed personal credentials.
2024.3.31.0
- Back up your Remote Desktop Manager data before upgrading
- Download Remote Desktop Manager version 2024.3.31.0 or later from the official Devolutions website (devolutions.net)
- Install or upgrade to the downloaded version
- Verify the fix by testing the My Personal Credentials password history and clear history functionality to confirm sensitive information is no longer exposed in shared vaults
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-1636 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-1636 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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