CVE-2022-2221
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 · uneditedInformation Exposure vulnerability in My Account Settings of Devolutions Remote Desktop Manager before 2022.1.8 allows authenticated users to access credentials of other users. This issue affects: Devolutions Remote Desktop Manager versions prior to 2022.1.8.
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 confidenceThis is an authentication-based broken access control vulnerability in Devolutions Remote Desktop Manager's My Account Settings feature. An authenticated user can view credentials belonging to other users, exposing sensitive credential data through improper authorization in the account settings functionality.
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.1.8CVSS 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 the application and navigate to Help > About, or check the installed programs list in Windows Control Panel to find the exact version numberAffected if The version displayed is lower than 2022.1.8 (for example, 2022.1.7, 2022.1.0, or any version in the 2021.x series)
-
Verify multi-user configurationCheck if more than one user account is configured or registered within the Remote Desktop Manager applicationAffected if Multiple user accounts exist in the system and the application uses the My Account Settings feature for credential management
-
Examine My Account Settings accessLog in as a standard authenticated user and navigate to the My Account Settings or equivalent user profile area where credentials are stored or displayedAffected if The interface allows viewing or lists credential entries associated with other user accounts, or shows credential data that should be restricted to the logged-in user only
-
Test cross-user credential visibilityCreate two separate user sessions or use an account with limited privileges and attempt to access credentials through the account settings panelAffected if An authenticated user can see, access, or export credentials belonging to a different user account without administrative elevation
You are affected if your installed Remote Desktop Manager version is below 2022.1.8 and the My Account Settings feature exposes credentials from other user accounts to authenticated users who should not have access to them.
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.1.8
Update Devolutions Remote Desktop Manager to version 2022.1.8 or later to obtain the vendor patch. Verify that user credential access controls are properly enforced after updating.
2022.1.8
- 1. Back up your current Remote Desktop Manager configuration and data
- 2. Download Remote Desktop Manager version 2022.1.8 or later from the official Devolutions website
- 3. Install the new version following the vendor's installation instructions
- 4. Verify the installation was successful
- 5. Test that the My Account Settings functionality works correctly
- 6. Confirm that users can no longer access credentials of other users
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2221 — 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-2221 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