dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2025-2003

HIGH · 7.1 CVSS v3.1 Published 2025-03-05
Fix available
A fix is available. Upgrade to 2024.3.13.0 or later.
See remediation →
77/100
Remediation priority · High
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 PAM vaults in Devolutions Server 2024.3.12 and earlier allows an authenticated user to bypass the 'add in root' 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

This is an authorization bypass vulnerability in Devolutions Server's PAM (Privileged Access Management) vault functionality. An authenticated user with limited privileges can bypass the 'add in root' permission check, allowing them to add entries to root-level vault folders they should not have access to. The vulnerability stems from incorrect authorization logic in the vault permission enforcement.

MitigationUpdate Devolutions Server to version 2024.3.13 or later to obtain the fix. Conduct a security audit of PAM vault access logs to identify any unauthorized root-level entries that may have been added during the vulnerability window, and review user role assignments.

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.13.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
None
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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. Identify installed Devolutions Server version
    Open the Devolutions Server Administration Console, navigate to 'About' or 'Licensing' section, or run: Launch the Server Manager, go to Help > About to view the exact version number
    Affected if Version is shown as lower than 2024.3.13.0 (e.g., 2024.3.12.0, 2024.2.x, etc.)
  2. Verify PAM vault module is in use
    In the Administration Console, navigate to the PAM section or 'Password Vault' feature. Confirm that Privileged Access Management vault functionality is enabled and has active user entries or folders
    Affected if PAM vault is enabled and contains active folders or entries
  3. Review PAM vault user role assignments
    In Administration Console, go to 'Users' or 'Roles' and examine which users are assigned to PAM vault roles. Specifically identify users who have limited privileges (e.g., not 'Vault Administrator' but have some vault access)
    Affected if Any users have PAM vault access roles other than full administrative access
  4. Audit PAM vault access logs for unauthorized root additions
    In the Server Manager, navigate to Logs or Audit Trail. Filter for PAM vault events, specifically 'Add Entry' or 'Create' actions at the root folder level. Look for entries added by users without 'Add in Root' permission
    Affected if Log entries show entries added to root-level folders by users who should not have that permission based on their role

Your environment is affected if Devolutions Server version is below 2024.3.13.0 AND PAM vault is actively used with users having non-administrative vault permissions.

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.13.0 or later
Fixed in 2024.3.13.0
Interim mitigation

Update Devolutions Server to version 2024.3.13 or later to obtain the fix. Conduct a security audit of PAM vault access logs to identify any unauthorized root-level entries that may have been added during the vulnerability window, and review user role assignments.

Recommended fix High confidence

2024.3.13.0 or later

  1. Identify the current Devolutions Server version in use
  2. Download Devolutions Server version 2024.3.13.0 or later from the official Devolutions website
  3. Review release notes for version 2024.3.13.0 to confirm the security fix is included
  4. Backup the current Devolutions Server configuration and database
  5. Perform the upgrade following the standard Devolutions Server upgrade procedure
  6. After upgrade, verify that the 'add in root' permission is correctly enforced in PAM vaults
  7. Test that authenticated users can no longer bypass the 'add in root' permission

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

Fix this in Devolutions Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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