CVE-2023-5358
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 Report log filters feature in Devolutions Server 2023.2.10.0 and earlier allows attackers to retrieve logs from vaults or entries they are not allowed to access via the report request url query parameters.
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 confidenceImproper access control in the Report log filters feature of Devolutions Server 2023.2.10.0 and earlier allows authenticated users to bypass authorization checks by manipulating URL query parameters in report requests, enabling access to logs from vaults or entries the user should not have permission to view.
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< 2023.3.4.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 versionCheck the installed version of Devolutions Server (typically via the administration console, installer properties, or server about page). Compare against the affected range: versions prior to 2023.3.4.0 are vulnerable.Affected if The installed version is 2023.2.10.0 or earlier, or any version below 2023.3.4.0
-
Verify Report log filters feature is accessibleConfirm the Report feature is enabled and accessible to authenticated users in the Devolutions Server configuration.Affected if The Report log filters feature is enabled and available to standard authenticated users
-
Review user permissions on Report featureExamine the permission model for the Report feature in the server administration panel to determine if users can generate reports on vault or entry logs.Affected if Standard authenticated users have permission to access the Report feature without restrictive row-level security filters
-
Audit report request logs for unauthorized accessReview server audit logs or web server logs for report requests that contain unusual or unexpected vault/entry identifiers in URL query parameters, which may indicate exploitation attempts.Affected if Evidence exists of report requests accessing vault or entry identifiers outside the user's normal permissions
A user is affected if running Devolutions Server version 2023.3.3.0 or earlier AND the Report log filters feature is accessible to authenticated users who could potentially manipulate query parameters.
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 · scoped2023.3.4.0
Apply the vendor patch for Devolutions Server 2023.2.10.0 or later. As a compensating control, audit user permissions on the Report feature and monitor for anomalous report requests accessing unexpected vault/entry identifiers.
2023.3.4.0
- Identify the current Devolutions Server version in use by accessing the administration console or checking the installed software
- Download Devolutions Server version 2023.3.4.0 or later from the official Devolutions website
- Review the release notes for version 2023.3.4.0 to understand any configuration or migration requirements
- Create a complete backup of the current Devolutions Server database and configuration
- Stop the Devolutions Server service before applying the update
- Install the updated version 2023.3.4.0 using the standard upgrade procedure
- Verify the installation completed successfully and the service started without errors
- Confirm the version number reflects 2023.3.4.0 or later in the administration console
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5358 — 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-5358 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