CVE-2023-5766
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 · uneditedA remote code execution vulnerability in Remote Desktop Manager 2023.2.33 and earlier on Windows allows an attacker to remotely execute code from another windows user session on the same host via a specially crafted TCP packet.
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 confidenceA remote code execution vulnerability in Remote Desktop Manager versions 2023.2.33 and earlier for Windows allows an attacker to execute arbitrary code in another Windows user session on the same host by sending specially crafted TCP packets. The vulnerability is network-exploitable but requires access to the same Windows host.
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<= 2023.2.33CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Remote Desktop Manager is installedCheck for the application in the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or look for the Devolutions folder in Program Files (x86) or Program FilesAffected if The application is found on the system
-
Locate the Remote Desktop Manager executableNavigate to the installation directory (typically C:\Program Files (x86)\Remote Desktop Manager or C:\Program Files\Remote Desktop Manager) and locate RemoteDesktopManager.exeAffected if The executable exists at the expected path
-
Retrieve the installed version numberRight-click on RemoteDesktopManager.exe, select Properties, then inspect the Details tab for the Product Version field; alternatively, run "Get-ItemProperty -Path 'C:\Program Files (x86)\Remote Desktop Manager\RemoteDesktopManager.exe' | Select-Object VersionInfo" in PowerShellAffected if The version returned is 2023.2.33 or lower
-
Confirm the version is within affected rangeCompare the extracted version to the affected range <=2023.2.33Affected if The version number is 2023.2.33 or any version lower than 2023.2.33
If Remote Desktop Manager is installed and the version is 2023.2.33 or earlier, the system is affected by CVE-2023-5766.
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 · scopedUpgrade Remote Desktop Manager to a version newer than 2023.2.33. Until patched, restrict network access to systems running the affected software and limit local user session privileges.
Version newer than 2023.2.33 (e.g., 2023.3.x or later stable release)
- Navigate to the official Devolutions website (devolutions.net) and locate the Remote Desktop Manager download page
- Download the latest version of Remote Desktop Manager for Windows
- Close any running instances of Remote Desktop Manager
- Run the installer and follow the prompts to upgrade the software
- After installation, verify the installed version is newer than 2023.2.33
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5766 — 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-2023-5766 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