CVE-2022-4287
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 · uneditedAuthentication bypass in local application lock feature in Devolutions Remote Desktop Manager 2022.3.26 and earlier on Windows allows malicious user to access the application.
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 confidenceThe vulnerability is an authentication bypass in the local application lock feature of Devolutions Remote Desktop Manager version 2022.3.26 and earlier on Windows. A malicious user can circumvent the lock mechanism to gain unauthorized access to the application, bypassing intended security controls.
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< 2022.3.27CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Check installed Remote Desktop Manager versionOpen Windows Control Panel > Programs and Features, or right-click the application shortcut and select Properties, or go to Help > About within the application to find the exact version numberAffected if The installed version is 2022.3.26 or earlier (any version below 2022.3.27)
-
Verify the local application lock feature statusLaunch Remote Desktop Manager and examine if a master password, PIN, or biometric lock is configured under Security settings or the lock icon in the toolbarAffected if The application lock feature is enabled or has been configured with a password/PIN
-
Confirm the application executable versionLocate the RemoteDesktopManager.exe file (typically in C:\Program Files\Devolutions\Remote Desktop Manager or C:\Program Files (x86)\Devolutions\Remote Desktop Manager), right-click, select Properties, and check the File version on the Details tabAffected if The file version shown is prior to 2022.3.27
You are affected if the installed version is 2022.3.26 or earlier AND the local application lock feature is enabled or was previously configured, as the vulnerability allows bypassing this security control.
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 · scoped2022.3.27
Update Devolutions Remote Desktop Manager to a version newer than 2022.3.26 to obtain the vendor patch. Verify that the application lock feature functions correctly after the update.
Remote Desktop Manager 2022.3.27
- Download Remote Desktop Manager version 2022.3.27 or later from the official Devolutions website
- Verify the download matches the correct version number before installation
- Close all instances of Remote Desktop Manager
- Install the updated version, ensuring the upgrade completes successfully
- Launch the application and verify the local application lock feature now properly requires authentication
- Confirm the version number in the application matches 2022.3.27 or later
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-2022-4287 — 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-2022-4287 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