dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2023-5240

HIGH · 7.5 CVSS v3.1 Published 2023-10-13
Fix available
A fix is available. Upgrade to after 2023.2.8.0 or later.
See remediation →
84/100
Remediation priority · High
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 access control in PAM propagation scripts in Devolutions Server 2023.2.8.0 and ealier allows an attack with permission to manage PAM propagation scripts to retrieve passwords stored in it via a GET request.

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 access control in PAM propagation scripts in Devolutions Server 2023.2.8.0 and earlier allows authenticated users with PAM script management permissions to retrieve stored passwords via insecure GET requests, exposing sensitive credentials through URL parameters and logs.

MitigationUpgrade Devolutions Server to a version beyond 2023.2.8.0 which contains the proper fix, and audit access controls for PAM propagation script management permissions.

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:<= 2023.2.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify Devolutions Server version
    Check the installed Devolutions Server version in the application or system information panel, or retrieve it via the server's built-in version check mechanism.
    Affected if The installed version is 2023.2.8.0 or earlier.
  2. Confirm PAM propagation scripts are enabled
    Inspect the PAM configuration or settings in Devolutions Server to determine if propagation scripts are configured and active.
    Affected if PAM propagation scripts are enabled or configured in the environment.
  3. Review PAM script management permissions
    Examine user role permissions or access control settings to identify accounts that have PAM script management privileges.
    Affected if Users exist with PAM script management permissions granted.
  4. Audit web server and application logs
    Search logs for GET requests containing URL parameters that may include credentials or sensitive data, particularly those related to PAM script operations.
    Affected if Logs contain GET requests with credentials or sensitive parameters exposed in URLs.
  5. Inspect proxy and firewall logs
    Review upstream proxy, WAF, or firewall logs for outgoing requests from the Devolutions Server that may have exposed credentials in URL query strings.
    Affected if External logs reveal credentials passed via GET request parameters.

A user is affected if running Devolutions Server version 2023.2.8.0 or earlier with PAM propagation scripts enabled and users possessing PAM script management permissions, where logs may have captured credentials in URL parameters.

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 2023.2.8.0
Interim mitigation

Upgrade Devolutions Server to a version beyond 2023.2.8.0 which contains the proper fix, and audit access controls for PAM propagation script management permissions.

Recommended fix Moderate confidence

Devolutions Server 2023.2.9.0 or later

  1. 1. Identify the current Devolutions Server version in use by checking the About or Version section of the administration console
  2. 2. Download the latest stable version of Devolutions Server from the official Devolutions website (devolutions.net) or your authorized distribution channel
  3. 3. Before upgrading, perform a complete backup of the Devolutions Server database and configuration files
  4. 4. Stop the Devolutions Server service
  5. 5. Install the latest version (2023.2.9.0 or later) following the standard upgrade procedure
  6. 6. After installation, verify the PAM propagation scripts functionality works correctly
  7. 7. Confirm the vulnerability is remediated by testing that unauthorized users cannot retrieve passwords via GET requests to PAM propagation scripts
Caveat Review release notes for any configuration or feature changes between versions; test in non-production environment first

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-2023-5240 — 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-2023-5240 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