dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2023-0952

MEDIUM · 6.5 CVSS v3.1 Published 2023-03-01
Fix available
A fix is available. Upgrade to after 2022.3.12 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 access controls on entries in Devolutions Server 2022.3.12 and earlier could allow an authenticated user to access sensitive data without proper authorization.

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 Devolutions Server versions 2022.3.12 and earlier allows authenticated users to bypass authorization checks and access sensitive data entries they should not have permission to view.

MitigationUpdate Devolutions Server to version 2022.3.13 or later which contains the access control fix, and verify proper authorization enforcement on sensitive data entries.

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:<= 2022.3.12

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. Identify Devolutions Server version
    Check the installed Devolutions Server version through the server administration interface, or use the product's built-in version check feature (typically found in Help > About or the administration dashboard)
    Affected if The installed version is 2022.3.12 or earlier
  2. Confirm authentication is enabled
    Verify that user authentication is configured and active on the Devolutions Server instance
    Affected if Authentication is enabled and users can log in to the system
  3. Verify sensitive data entries exist
    Check whether the server contains any sensitive data entries such as passwords, credentials, or confidential records stored in vaults or password repositories
    Affected if Sensitive data entries are stored in the system
  4. Review user permissions configuration
    Examine the user or group permission settings for sensitive data entries to determine if proper access controls and authorization rules are defined
    Affected if Users have been granted granular permissions on sensitive entries (the vulnerability allows bypassing these permissions)

A user is affected if they are running Devolutions Server version 2022.3.12 or earlier with authentication enabled and have sensitive data entries stored, regardless of configured permissions.

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

Update Devolutions Server to version 2022.3.13 or later which contains the access control fix, and verify proper authorization enforcement on sensitive data entries.

Recommended fix Moderate confidence

Devolutions Server 2022.3.13 or later (latest stable release)

  1. 1. Identify the current installed version of Devolutions Server by checking the application or system information
  2. 2. Navigate to the official Devolutions download page at devolutions.net or the Devolutions Server download section
  3. 3. Download the latest stable version of Devolutions Server (version 2022.3.13 or later)
  4. 4. Review the release notes for version 2022.3.13 or later to confirm the security fix for CVE-2023-0952 is included
  5. 5. Create a backup of the existing Devolutions Server database and configuration files
  6. 6. Stop the Devolutions Server service before upgrading
  7. 7. Install the new version following the standard upgrade procedure documented by Devolutions
  8. 8. Start the Devolutions Server service after installation completes
Caveat Review release notes for any configuration changes or migration requirements between versions; test in a 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
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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