dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2024-1900

MEDIUM · 5.5 CVSS v3.1 Published 2024-03-05
Fix available
A fix is available. Upgrade to after 2023.3.16.0 or later.
See remediation →
57/100
Remediation priority · Elevated
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 session management in the identity provider authentication flow in Devolutions Server 2023.3.14.0 and earlier allows an authenticated user via an identity provider to stay authenticated after his user is disabled or deleted in the identity provider such as Okta or Microsoft O365. The user will stay authenticated until the Devolutions Server token expiration.

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

Devolutions Server does not properly validate user status with the identity provider during session management, allowing authenticated sessions to persist even after a user's account is disabled or deleted in the IdP (Okta, Microsoft O365). Sessions remain valid until the Devolutions Server token expires rather than being invalidated upon IdP user state changes.

MitigationImplement real-time or near-real-time session validation against the identity provider to revoke sessions when a user's account is disabled or deleted, or reduce token expiration times to limit the window of unauthorized access.

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.3.16.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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:A/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 version
    Check the installed version of Devolutions Server in your environment. This is typically found in the application itself under About or in the installation directory. Compare your version against the affected range: any version <= 2023.3.16.0
    Affected if The installed version is 2023.3.16.0 or lower
  2. Confirm SAML/SSO IdP authentication is enabled
    Check if Devolutions Server is configured to use SAML-based single sign-on with an external identity provider, specifically Okta or Microsoft O365. This is typically configured in the authentication or security settings of the Devolutions Server admin console
    Affected if SAML authentication with Okta or Microsoft O365 is active and in use
  3. Review session token expiration settings
    Inspect the configured token or session lifetime settings in Devolutions Server. Look for the token expiration duration configured for SAML sessions
    Affected if Token expiration is set to a long duration (hours to days), creating a window where stale sessions remain valid
  4. Verify IdP user state synchronization
    Determine whether Devolutions Server has any mechanism to periodically query the identity provider to validate that the user account is still active, enabled, and not deleted. Check if there is any integration that pulls user status changes from Okta or Microsoft O365 in near-real-time
    Affected if No real-time or near-real-time synchronization with the IdP exists; user state changes in the IdP are not reflected in active sessions
  5. Check session invalidation configuration
    Review the session management configuration to see if there is any mechanism to revoke active sessions when the user's account becomes disabled or deleted in the identity provider
    Affected if Sessions are not automatically invalidated when a user is disabled or deleted in the IdP; sessions remain active until natural token expiration

You are affected if you run Devolutions Server version 2023.3.16.0 or lower with SAML/SSO authentication (Okta or Microsoft O365) and do not have real-time session validation against the IdP 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 a release after 2023.3.16.0
Interim mitigation

Implement real-time or near-real-time session validation against the identity provider to revoke sessions when a user's account is disabled or deleted, or reduce token expiration times to limit the window of unauthorized access.

Recommended fix Moderate confidence

Devolutions Server 2023.3.17.0 or later

  1. 1. Identify the current installed version of Devolutions Server by accessing the Administration section in the web interface or checking the installed software.
  2. 2. Backup the Devolutions Server database and configuration files before performing any upgrade.
  3. 3. Download the latest version of Devolutions Server from the official Devolutions download page at devolutions.net/server or your licensed download area.
  4. 4. Stop the Devolutions Server service before applying the update.
  5. 5. Install the update following the standard Devolutions Server upgrade procedure.
  6. 6. Restart the Devolutions Server service after installation completes.
  7. 7. Verify that users authenticated via identity provider (Okta, Microsoft O365) are now properly de-authenticated when disabled or deleted in the identity provider.
Caveat Review release notes for potential breaking 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
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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