CVE-2023-0661
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 · uneditedImproper access control in Devolutions Server allows an authenticated user to access unauthorized sensitive data.
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 confidenceImproper access control in Devolutions Server allows an authenticated user to bypass intended authorization boundaries and access sensitive data they are not permitted to view. This is an authorization vulnerability where the application fails to properly validate user permissions before granting access to protected resources.
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>= 2022.3.1.0, < 2022.3.10.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Devolutions Server installationLocate the Devolutions Server installation directory or check installed programs list to confirm Devolutions Server is present on the systemAffected if Devolutions Server is installed on the machine
-
Determine installed versionCheck the installed version of Devolutions Server - this is typically found in the application itself, about section, or Windows Programs and Features. Compare the version number against the affected range 2022.3.1.0 to 2022.3.9.xAffected if The installed version is >= 2022.3.1.0 and < 2022.3.10.0
-
Confirm web interface accessibilityVerify the Devolutions Server web interface is accessible - this is typically hosted on a configured port (check IIS or the service configuration for the binding)Affected if The web interface is accessible and the version is within the affected range
-
Verify multi-user or AD/LDAP authentication is configuredCheck if the server is configured to allow multiple user accounts or integrate with Active Directory/LDAP - this vulnerability requires an authenticated user context to exploit the authorization bypassAffected if Multiple user accounts or external directory authentication is enabled and the version is vulnerable
A user is affected if Devolutions Server version 2022.3.1.0 through 2022.3.9.x is installed with user authentication enabled, allowing an authenticated but low-privilege user to potentially bypass authorization checks.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2022.3.10.0
Implement and enforce proper authorization checks across all data access points, ensuring that users can only access resources for which they have explicit permissions. Review and strengthen role-based access control (RBAC) mechanisms.
2022.3.10.0 or later stable release
- Identify the current Devolutions Server version in use by checking the About or version information in the application
- Confirm the installed version falls within the vulnerable range: >= 2022.3.1.0 and < 2022.3.10.0
- Plan and schedule an upgrade window following organizational change management procedures
- Obtain the fixed version (2022.3.10.0 or later stable release) from the official Devolutions download portal at devolutions.net
- Execute the upgrade following standard Devolutions Server upgrade documentation
- Verify the upgrade was successful by confirming the new version number
- Test critical functionality to ensure the upgrade did not introduce regressions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2023-0661 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-0661 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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