dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2024-12196

MEDIUM · 6.5 CVSS v3.1 Published 2024-12-04
Fix available
A fix is available. Upgrade to 2024.3.8.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Incorrect authorization in the permission component in Devolutions Server 2024.3.7.0 and earlier allows an authenticated user to view the password history of an entry without the view password permission.

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 confidence

Devolutions Server 2024.3.7.0 and earlier contains an incorrect authorization vulnerability in its permission component. An authenticated user with limited privileges can bypass the view password permission check to access password history for entries they should not have access to view.

MitigationUpgrade to Devolutions Server version 2024.3.8.0 or later which contains the patched permission validation. If immediate patching is not possible, review and restrict user role assignments as a compensating control.

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
Devolutions ServerApplication
Affected:< 2024.3.8.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Devolutions Server version
    Check the installed version of Devolutions Server. This is typically found in the application itself under Help > About, or in the Windows Programs and Features list. Compare the version number to the affected range: any version prior to 2024.3.8.0 is vulnerable.
    Affected if The installed version is 2024.3.7.0 or earlier, or any version below 2024.3.8.0.
  2. Verify password history feature is in use
    Check if any password entries in Devolutions Server have password history enabled or stored. This can be done by examining entry properties or running a report on entries that contain password history records.
    Affected if Password history is enabled and contains historical passwords for entries that should have restricted access.
  3. Review user role assignments
    Identify users who are assigned roles with limited privileges, specifically those with view password permission restrictions. Check which vault entries these users have access to and whether any entries they can access contain password history.
    Affected if There exist non-admin users with restricted password view permissions who have access to vault entries containing password history.
  4. Test authorization boundary
    As an authenticated user with limited privileges (non-administrator role), attempt to access password history for an entry the user should only have limited access to. Log in with a low-privilege account and check if password history is visible when it should be hidden by permission settings.
    Affected if A limited-privilege user can view password history for entries they should not have permission to see.

You are affected if your Devolutions Server version is below 2024.3.8.0 and you have users with restricted password view permissions accessing vault entries that contain password history.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2024.3.8.0 or later
Fixed in 2024.3.8.0
Interim mitigation

Upgrade to Devolutions Server version 2024.3.8.0 or later which contains the patched permission validation. If immediate patching is not possible, review and restrict user role assignments as a compensating control.

Recommended fix High confidence

2024.3.8.0 or later

  1. Create a complete backup of your Devolutions Server database and configuration files before proceeding with any upgrade.
  2. Stop the Devolutions Server service to ensure no active connections during the upgrade process.
  3. Download Devolutions Server version 2024.3.8.0 or later from the official Devolutions download repository at devolutions.net.
  4. Execute the installer or follow the documented upgrade procedure for your deployment type (fresh install or in-place upgrade).
  5. Restart the Devolutions Server service after the upgrade completes.
  6. Verify the upgrade was successful by checking the server version in the administration console.
  7. Confirm that the authorization fix is working by testing that users without 'view password' permission can no longer access password history for entries they don't have permission to view.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Devolutions Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12196 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-12196 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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