dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2025-3517

MEDIUM · 6.3 CVSS v3.1 Published 2025-05-01
Fix available
A fix is available. Upgrade to 2025.1.6.0 or later.
See remediation →
69/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 privilege assignment in PAM JIT elevation feature in Devolutions Server 2025.1.5.0 and earlier allows a PAM user to elevate a previously configured user configured in a PAM JIT account via failure to update the internal account’s SID when updating the username.

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

A vulnerability in Devolutions Server's PAM JIT elevation feature fails to update the internal Security Identifier (SID) when a username is modified in a PAM JIT account configuration. This incorrect privilege assignment allows a PAM user to potentially elevate with misaligned privileges from a previously configured account.

MitigationUpdate Devolutions Server to a version beyond 2025.1.5.0 once the patch is available, or carefully audit and reconfigure existing PAM JIT accounts to ensure username-to-SID mappings are correct.

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:< 2025.1.6.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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/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. Identify Devolutions Server installation and version
    Locate the Devolutions Server installation directory and check the version. Common paths include C:\Program Files\Devolutions\Server or check Windows Programs and Features. Look for version information in the application or associated files.
    Affected if The installed version is lower than 2025.1.6.0 (e.g., 2025.1.5.0 or earlier)
  2. Confirm PAM JIT elevation feature is configured
    Access Devolutions Server administration interface and navigate to the PAM (Privileged Access Management) section. Check if any JIT (Just-In-Time) elevation configurations exist for granting privileged access.
    Affected if PAM JIT accounts or elevation configurations are present in the system
  3. Review PAM JIT account usernames for modifications
    Examine all PAM JIT account entries in the Devolutions Server configuration or database. Compare the currently configured username against historical records or audit logs to identify any accounts where the username was changed after initial configuration.
    Affected if Any PAM JIT account has a username that was modified after initial setup, indicating a potential stale SID mapping
  4. Audit privilege assignments for PAM users
    Review the assigned privileges and permissions for PAM-managed accounts. Check if the effective permissions align with the current username configuration rather than any previous username that may have been linked to a different SID.
    Affected if PAM users have privileges that do not match their current username or appear to derive from a different account configuration

A user is affected if their Devolutions Server version is below 2025.1.6.0 AND they have PAM JIT accounts with usernames that were modified after initial configuration, potentially causing privilege misalignment from outdated SID mappings.

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 2025.1.6.0 or later
Fixed in 2025.1.6.0
Interim mitigation

Update Devolutions Server to a version beyond 2025.1.5.0 once the patch is available, or carefully audit and reconfigure existing PAM JIT accounts to ensure username-to-SID mappings are correct.

Recommended fix High confidence

2025.1.6.0

  1. 1. Back up the current Devolutions Server database and configuration
  2. 2. Download Devolutions Server version 2025.1.6.0 or later from the official source (devolutions.net)
  3. 3. Stop the Devolutions Server service
  4. 4. Install the updated version following standard upgrade procedures
  5. 5. Verify the PAM JIT elevation feature now correctly updates the internal SID when usernames are modified
  6. 6. Restart the Devolutions Server service
  7. 7. Test that PAM users can no longer elevate privileges through the described attack vector

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
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,420
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,872.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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