dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2023-1603

MEDIUM · 6.5 CVSS v3.1 Published 2023-04-02
Fix available
A fix is available. Upgrade to 2023.1.3.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
Permission bypass when importing or synchronizing entries in User vault in Devolutions Server 2022.3.13 and prior versions allows users with restricted rights to bypass entry permission via id collision.

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

Devolutions Server 2022.3.13 and prior versions contain a permission bypass vulnerability in the User vault import and synchronization functionality. Users with restricted rights can exploit an ID collision vulnerability to gain unauthorized access to entries they should not have permission to view or modify.

MitigationUpgrade Devolutions Server to a version newer than 2022.3.13. Until patching is possible, restrict import/sync permissions for low-privilege users and audit vault access logs for suspicious activity.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 installed Devolutions Server version
    Check the installed version of Devolutions Server in your environment (typically via the installed software list, server admin console, or About section). Compare it against the vulnerable range: versions prior to 2023.1.3.0 (including 2022.3.13 and earlier).
    Affected if The installed version is lower than 2023.1.3.0 (e.g., 2022.3.x, 2022.2.x, etc.).
  2. Confirm User vault import/sync feature is in use
    Review system logs, audit logs, or configuration settings to determine whether the User vault import or synchronization functionality has been enabled or utilized in your deployment.
    Affected if The vault import/sync feature is enabled or has been used, and the version is vulnerable.
  3. Audit vault access logs for unauthorized entry access
    Review vault access logs or audit trails for entries where low-privilege users accessed records outside their normal permission scope, particularly around import/sync operations.
    Affected if Logs show users with restricted rights accessing vault entries they should not have permission to view or modify, especially following import/sync actions.
  4. Inspect for permission anomalies in vault entries
    Examine vault entry ownership and permission assignments for signs of ID collision exploitation, such as entries suddenly showing different owners or unexpected access grants.
    Affected if Vault entries display unexpected ownership changes or permission assignments that do not align with configured access controls.

You are affected if Devolutions Server version is below 2023.1.3.0 and the User vault import/sync functionality is in use, with evidence of unauthorized access to vault entries by low-privilege users.

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

Upgrade Devolutions Server to a version newer than 2022.3.13. Until patching is possible, restrict import/sync permissions for low-privilege users and audit vault access logs for suspicious activity.

Recommended fix High confidence

2023.1.3.0

  1. 1. Back up your current Devolutions Server database and configuration
  2. 2. Review the official Devolutions Server 2023.1.3.0 release notes at devolutions.net for any specific upgrade requirements
  3. 3. Download Devolutions Server version 2023.1.3.0 or later from the official vendor source
  4. 4. Stop the Devolutions Server service before applying the update
  5. 5. Apply the upgrade following the vendor's documented upgrade procedure
  6. 6. Verify the service starts successfully after upgrade
  7. 7. Test that restricted users can no longer bypass entry permissions when importing or synchronizing entries in User vault
  8. 8. Monitor logs to confirm normal operation

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