CVE-2023-2282
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 access control in the Web Login listener in Devolutions Remote Desktop Manager 2023.1.22 and earlier on Windows allows an authenticated user to bypass administrator-enforced Web Login restrictions and gain access to entries via an unexpected vector.
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 confidenceImproper access control in the Web Login listener of Devolutions Remote Desktop Manager 2023.1.22 and earlier on Windows allows authenticated users to bypass administrator-enforced Web Login restrictions and access entries through an unexpected vector.
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.1.22CVSS 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.
-
Check installed version of Remote Desktop ManagerOpen Remote Desktop Manager and navigate to Help > About, or check the Windows Programs and Features list to confirm the exact version number installed.Affected if The installed version is 2023.1.22 or earlier.
-
Verify Web Login feature is enabledCheck the Remote Desktop Manager configuration for Web Login settings, typically found in the application settings or connection properties where Web Login entries are defined.Affected if Web Login entries or the Web Login listener feature is configured and active in the application.
-
Confirm presence of administrator-enforced restrictionsReview whether administrator-defined Web Login restrictions or entry access controls are in place within the application, typically managed through admin-defined security policies or entry-level restrictions.Affected if Administrator-enforced Web Login restrictions or access controls have been configured for the environment.
If the installed Remote Desktop Manager version is 2023.1.22 or earlier, Web Login is enabled, and administrator restrictions exist, the environment is vulnerable to the access control bypass.
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 to Remote Desktop Manager version 2023.1.23 or later to receive the access control fix.
Remote Desktop Manager 2023.1.23 or later
- 1. Verify current installation version of Remote Desktop Manager by opening the application and navigating to Help > About
- 2. Download the latest version of Remote Desktop Manager from the official Devolutions website (devolutions.net)
- 3. Close Remote Desktop Manager completely before installing the update
- 4. Run the installer and follow the on-screen prompts to complete the upgrade
- 5. After installation, verify the new version by checking Help > About to confirm the version is newer than 2023.1.22
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-2282 — 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-2282 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