dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2025-4493

MEDIUM · 6.5 CVSS v3.1 Published 2025-05-28
Fix available
A fix is available. Upgrade to after 2025.1.7.0 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Improper privilege assignment in PAM JIT privilege sets in Devolutions Server allows a PAM user to perform PAM JIT requests on unauthorized groups by exploiting a user interface issue. This issue affects the following versions :  * Devolutions Server 2025.1.3.0 through 2025.1.7.0 * Devolutions Server 2024.3.15.0 and earlier

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

Improper privilege assignment in PAM JIT privilege sets in Devolutions Server allows authenticated PAM users to perform Just-In-Time requests on groups they are not authorized to access, due to a user interface issue that bypasses intended authorization controls.

MitigationUpgrade to Devolutions Server 2025.1.8.0 or later, or 2024.3.16.0 or later. Review PAM JIT privilege set configurations to ensure proper group access controls are enforced.

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.15.0>= 2025.1.3.0, <= 2025.1.7.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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 installation
    Locate the Devolutions Server installation and determine the installed version number. Check the application's About or version information page, or check the installation directory for version metadata.
    Affected if The installed version is 2024.3.15.0 or lower, OR between 2025.1.3.0 and 2025.1.7.0 inclusive.
  2. Confirm PAM module is configured
    Verify if the Privileged Access Management (PAM) module is enabled in the Devolutions Server configuration. Check the server settings or configuration files for PAM-related settings.
    Affected if PAM is enabled and configured on the server.
  3. Check for JIT privilege set configurations
    Review the PAM Just-In-Time (JIT) privilege set configurations. Access the PAM settings in the Devolutions Server administration interface and examine any defined JIT privilege sets.
    Affected if One or more JIT privilege sets are configured in the PAM module.
  4. Review group access assignments in JIT sets
    Inspect the group memberships and access assignments within each JIT privilege set. Verify which user groups are permitted to request elevated access through the JIT mechanism.
    Affected if JIT privilege sets exist and assign group access permissions (the vulnerability allows bypass of these authorization checks).

A defender is affected if they run a vulnerable Devolutions Server version (2024.3.15.0 or lower, or 2025.1.3.0 to 2025.1.7.0) and have PAM with JIT privilege sets configured, regardless of how the groups are assigned.

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 a release after 2025.1.7.0
Interim mitigation

Upgrade to Devolutions Server 2025.1.8.0 or later, or 2024.3.16.0 or later. Review PAM JIT privilege set configurations to ensure proper group access controls are enforced.

Recommended fix Moderate confidence

2024.3.16.0 or later for 2024.x branches; 2025.1.8.0 or later for 2025.x branches

  1. 1. Identify the current Devolutions Server version installed using the Server Manager or Administration console.
  2. 2. For versions <= 2024.3.15.0: Upgrade to version 2024.3.16.0 or later.
  3. 3. For versions >= 2025.1.3.0 and <= 2025.1.7.0: Upgrade to version 2025.1.8.0 or later.
  4. 4. After upgrading, verify the PAM JIT privilege set configuration in the administration interface to confirm the fix is applied.
  5. 5. Test PAM JIT functionality with authorized and unauthorized groups to validate the privilege assignment is now correct.
Caveat Review release notes for any schema or configuration changes between versions before upgrading in production environments

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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