dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2024-5072

MEDIUM · 6.5 CVSS v3.1 Published 2024-05-17
Fix available
A fix is available. Upgrade to 2024.1.12.0 or later.
See remediation →
71/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
Improper input validation in PAM JIT elevation feature in Devolutions Server 2024.1.11.0 and earlier allows an authenticated user with access to the PAM JIT elevation feature to manipulate the LDAP filter query via a specially crafted 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 · high confidence

Improper input validation in the PAM JIT elevation feature allows authenticated users with access to this feature to manipulate LDAP filter queries through specially crafted requests, potentially enabling LDAP injection.

MitigationUpdate Devolutions Server to version 2024.1.12.0 or later. Until patched, limit access to the PAM JIT elevation feature to only trusted administrators and implement strict input validation on LDAP filter parameters.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Determine installed Devolutions Server version
    Access the Devolutions Server Administration Console or check the installed software version through the About section in the management interface, or run: dpkg -l | grep devolutions-server (Linux) or check Programs and Features (Windows)
    Affected if The installed version is below 2024.1.12.0
  2. Verify PAM JIT elevation feature status
    Navigate to Administration > PAM (Privileged Access Management) in the Devolutions Server web console and check if JIT (Just-In-Time) elevation is enabled or configured
    Affected if PAM JIT elevation is enabled or configured in the environment
  3. Check LDAP filter configuration in PAM settings
    In the PAM module settings, examine any LDAP filter fields or query configurations used for JIT elevation user/group resolution
    Affected if LDAP filters are defined in PAM JIT configuration without proper input validation controls
  4. Review authentication logs for suspicious LDAP injection patterns
    Examine Devolutions Server logs (typically in the Logs folder or via the audit trail) for anomalous LDAP filter strings in PAM JIT elevation requests, such as wildcard characters or unexpected operators like &(objectClass=*)(userPassword=*)
    Affected if Logs contain LDAP filter queries with injection-like patterns or unexpected LDAP syntax in PAM JIT elevation events

Environment is affected if running Devolutions Server version below 2024.1.12.0 AND the PAM JIT elevation feature is enabled with LDAP-based user filtering configured.

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.1.12.0 or later
Fixed in 2024.1.12.0
Interim mitigation

Update Devolutions Server to version 2024.1.12.0 or later. Until patched, limit access to the PAM JIT elevation feature to only trusted administrators and implement strict input validation on LDAP filter parameters.

Recommended fix High confidence

2024.1.12.0

  1. Download Devolutions Server version 2024.1.12.0 or later from the official Devolutions website (devolutions.net)
  2. Review the official release notes for any specific upgrade instructions
  3. Back up the current Devolutions Server database and configuration
  4. Install the upgrade following the standard Devolutions Server upgrade procedure
  5. Verify the PAM JIT elevation feature functions correctly after upgrade
  6. Confirm the LDAP filter query vulnerability is resolved

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-5072 — 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-5072 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