CVE-2023-2118
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 · uneditedInsufficient access control in support ticket feature in Devolutions Server 2023.1.5.0 and below allows an authenticated attacker to send support tickets and download diagnostic files via specific endpoints.
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 confidenceInsufficient access control in the support ticket feature of Devolutions Server 2023.1.5.0 and below allows authenticated attackers to send support tickets and download diagnostic files via specific endpoints that lack proper authorization validation.
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.1.6.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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 on the system. Common paths may include C:\Program Files\Devolutions\Server or similar. Check Windows Programs and Features for 'Devolutions Server'.Affected if Devolutions Server is installed on the system
-
Determine installed version numberCheck the version of Devolutions Server. This is typically visible in the application itself, in Windows Programs and Features, or in the installation directory's version info. Look for a version string like '2023.1.x.x' or similar.Affected if The installed version is 2023.1.5.0 or any version below 2023.1.6.0
-
Verify support ticket feature is accessibleAccess the Devolutions Server web interface and navigate to the support or help section where support tickets can be submitted. Log in with any valid user account.Affected if The support ticket feature is available and accessible through the web interface
-
Check for unauthorized endpoint accessIf you have access to server logs or can test web endpoints, look for or attempt to access support-related endpoints such as /api/support, /api/ticket, or similar diagnostic file download endpoints without proper admin authorization.Affected if Support ticket submission or diagnostic file download endpoints respond without requiring elevated privileges beyond basic authentication
The environment is affected if Devolutions Server version 2023.1.5.0 or below is installed and the support ticket feature is accessible to non-admin authenticated users.
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.1.6.0
Upgrade Devolutions Server to a version above 2023.1.5.0 that contains proper access control enforcement for the support ticket feature, or apply vendor-provided patches.
2023.1.6.0
- Upgrade Devolutions Server to version 2023.1.6.0 or later
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-2118 — 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-2118 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