CVE-2024-2403
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 · uneditedImproper cleanup in temporary file handling component in Devolutions Remote Desktop Manager 2024.1.12 and earlier on Windows allows an attacker that compromised a user endpoint, under specific circumstances, to access sensitive information via residual files in the temporary directory.
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.1.12 and earlier for Windows, the temporary file handling component fails to properly clean up residual files in the system's temp directory. An attacker with already-compromised access to the user's endpoint can potentially access sensitive information from these improperly deleted temporary files under specific circumstances.
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.1.15.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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/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 Remote Desktop Manager versionOpen Remote Desktop Manager, then go to Help > About, or open Windows Settings > Apps > Apps & features, and locate Devolutions Remote Desktop Manager to view the installed version numberAffected if The displayed version is 2024.1.12 or earlier, or any version below 2024.1.15.0
-
Compare version against affected rangeCompare your installed version number to the known affected range: any version lower than 2024.1.15.0 is considered vulnerableAffected if Your installed version is less than 2024.1.15.0 (for example, 2024.1.12, 2024.1.10, etc.)
-
Inspect system temp directory for residual filesNavigate to your system's temporary folder (typically %TEMP% or the application-specific temp location under %APPDATA%\Devolutions\RemoteDesktopManager\) and examine for files that may remain after closing the applicationAffected if You find residual files created by Remote Desktop Manager that persist after the application has been closed and should have been cleaned up
You are affected if your installed version of Devolutions Remote Desktop Manager is 2024.1.15.0 or earlier, meaning the temporary file cleanup vulnerability is present in your environment.
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.1.15.0
Upgrade to Remote Desktop Manager version 2024.1.13 or later, which contains the proper temporary file cleanup fix. As a interim measure, manually clear the application's temp directory after each session.
Remote Desktop Manager 2024.1.15.0 or later
- Verify current installed version of Remote Desktop Manager by checking Help > About
- Navigate to the official Devolutions download page at devolutions.net or the Devolutions Server management console
- Download Remote Desktop Manager version 2024.1.15.0 or later for Windows
- Run the installer and follow the on-screen prompts to complete the upgrade
- Restart Remote Desktop Manager after the upgrade completes
- Verify the new version by checking Help > About to confirm version 2024.1.15.0 or higher is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2403 — 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-2024-2403 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