CVE-2022-3781
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 · uneditedDashlane password and Keepass Server password in My Account Settings are not encrypted in the database in Devolutions Remote Desktop Manager 2022.2.26 and prior versions and Devolutions Server 2022.3.1 and prior versions which allows database users to read the data. This issue affects : Remote Desktop Manager 2022.2.26 and prior versions. Devolutions Server 2022.3.1 and prior versions.
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 confidenceSensitive credentials (Dashlane password and Keepass Server password) stored in user My Account Settings are persisted in plaintext/unencrypted in the database. An attacker with database access—whether through direct access, a compromised account, or SQL injection—can read these stored credentials in cleartext, leading to credential exposure.
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.2< 2022.2.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
- 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, go to Help > About, or check the installed version via Add/Remove Programs in Windows Control PanelAffected if Version is lower than 2022.2.27 (e.g., 2022.2.26 or earlier)
-
Check installed version of Devolutions ServerCheck the installed version through the Devolutions Server management console or Windows Add/Remove ProgramsAffected if Version is lower than 2022.3.2 (e.g., 2022.3.1 or earlier)
-
Inspect database for plaintext credential storageQuery the database for user account settings tables, looking for fields related to Dashlane password or Keepass Server password - these should appear in plaintext if the vulnerability existsAffected if Dashlane password or Keepass Server password fields contain readable plaintext values rather than encrypted data
-
Verify encryption of sensitive credential fieldsExamine the data schema for account-related tables, specifically fields storing Dashlane and Keepass credentials - compare against documentation to determine if encryption is appliedAffected if The credential storage fields do not use encryption or appear as plaintext strings
You are affected if you are running Remote Desktop Manager below 2022.2.27 or Devolutions Server below 2022.3.2 AND have stored Dashlane or Keepass Server passwords in My Account Settings, with those values appearing in plaintext in the database.
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.2.272022.3.2
Update to Remote Desktop Manager 2022.2.27+ and Devolutions Server 2022.3.2+ which encrypt these fields. Until patched, restrict database access strictly and monitor for unauthorized database queries.
Devolutions Server 2022.3.2 or later; Remote Desktop Manager 2022.2.27 or later
- Upgrade Devolutions Server to version 2022.3.2 or later
- Upgrade Remote Desktop Manager to version 2022.2.27 or later
- After upgrading, verify that passwords stored in My Account Settings are now encrypted in the database
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3781 — 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-3781 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