dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2024-12151

MEDIUM · 5.0 CVSS v3.1 Published 2024-12-04
Fix available
A fix is available. Upgrade to 2024.3.9.0 or later.
See remediation →
56/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 permission assignment in the user migration feature in Devolutions Server 2024.3.8.0 and earlier allows users to retain their old permission sets.

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 confidence

In Devolutions Server 2024.3.8.0 and earlier, the user migration feature has a logic flaw where users retain their old permission sets instead of receiving the intended new permission assignments during migration. This creates a potential for privilege escalation or unauthorized access if users migrate with higher permissions than they should have in the new system.

MitigationUpgrade to a version newer than 2024.3.8.0 when available. Review and manually reset permissions for any users who have migrated to ensure they have only the intended permission sets for their current role.

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.9.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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L

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. Check Devolutions Server version
    Determine the installed version of Devolutions Server and compare it to the affected range of versions prior to 2024.3.9.0
    Affected if The installed version is earlier than 2024.3.9.0
  2. Identify migration usage
    Review system logs, migration records, or configuration data to determine whether the user migration feature was used in this environment
    Affected if User migration was performed on the system
  3. Review migrated user permissions
    Inspect the current permission assignments for users who were migrated and compare them to the intended permission sets for their roles in the new system
    Affected if Migrated users have permissions that exceed or differ from what was intended for their current role
  4. Verify permission baseline
    Cross-reference actual user permissions against documented expected permissions for each user role after migration
    Affected if Discrepancies exist between assigned permissions and intended role-based permissions for migrated users

A user is affected if running Devolutions Server version earlier than 2024.3.9.0 AND the user migration feature was used, resulting in permission assignments that do not match the intended configuration for their role.

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.9.0 or later
Fixed in 2024.3.9.0
Interim mitigation

Upgrade to a version newer than 2024.3.8.0 when available. Review and manually reset permissions for any users who have migrated to ensure they have only the intended permission sets for their current role.

Recommended fix Moderate confidence

2024.3.9.0 or later

  1. Ensure you have a complete backup of your Devolutions Server database and configuration
  2. Review the Devolutions Server 2024.3.9.0 release notes for any migration requirements
  3. Stop the Devolutions Server service before beginning the upgrade
  4. Download Devolutions Server version 2024.3.9.0 or later from the official Devolutions download center
  5. Execute the installer and follow the on-screen upgrade procedure
  6. After installation, verify the user migration feature now correctly assigns new permission sets instead of retaining old ones
  7. Restart the Devolutions Server service
  8. Confirm normal operation and that users now receive appropriate permissions based on their current role assignments

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

Fix this in Devolutions Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12151 — 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-12151 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