CVE-2022-33996
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 · uneditedIncorrect permission management in Devolutions Server before 2022.2 allows a new user with a preexisting username to inherit the permissions of that previous user.
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 confidenceIn Devolutions Server versions before 2022.2, when a user account is deleted and a new account is created with the same username, the new account incorrectly inherits all permissions, roles, and access rights assigned to the previous account. This permission inheritance occurs due to improper handling of username reuse in the user management backend, allowing a new user to gain unintended elevated privileges.
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.2.0CVSS 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 Devolutions Server versionLocate the installed version of Devolutions Server through the administration console, About section, or installation directory version fileAffected if Version is before 2022.2.0
-
Review user account audit logsExamine user management logs or audit trails for instances where a user account was deleted and a new account was created with the identical usernameAffected if Any such username reuse events exist in the logs
-
Inspect permissions on reused username accountsFor accounts identified with reused usernames, compare their assigned roles, permissions, and access rights against what would be expected for a newly created accountAffected if Permissions exceed default new user permissions or match the previous account's permissions
Your environment is affected if you run Devolutions Server version before 2022.2 and you have any user accounts that were created with usernames previously assigned to deleted accounts.
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.0
Upgrade Devolutions Server to version 2022.2 or later, which contains the fix for proper permission management. Audit existing user accounts for any that may have been created with reused usernames to verify permissions are correctly scoped.
2022.2.0
- Backup the Devolutions Server database before starting the upgrade process
- Download Devolutions Server version 2022.2.0 or later from the official Devolutions website
- Stop the Devolutions Server service
- Run the installer/upgrade package for version 2022.2.0 or later
- Follow the installation wizard prompts to complete the upgrade
- Start the Devolutions Server service
- Verify the upgrade was successful by checking the server version
- Test that newly created users with previously existing usernames do NOT inherit permissions from deleted users with the same name
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33996 — 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-33996 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