dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2023-6264

MEDIUM · 5.3 CVSS v3.1 Published 2023-11-22
Fix available
A fix is available. Upgrade to 2023.3.8.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Information leak in Content-Security-Policy header in Devolutions Server 2023.3.7.0 allows an unauthenticated attacker to list the configured Devolutions Gateways 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 · high confidence

The Content-Security-Policy HTTP header in Devolutions Server 2023.3.7.0 is misconfigured or includes sensitive information that exposes configured Devolutions Gateway endpoints. An unauthenticated remote attacker can exploit this by sending HTTP requests and analyzing the CSP header response to enumerate internal gateway endpoint configurations.

MitigationUpdate Devolutions Server to version 2023.3.8.0 or later which contains the security fix, or configure the web server to strip or sanitize sensitive information from the Content-Security-Policy header before serving responses.

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.3.8.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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Devolutions Server installation
    Identify if Devolutions Server is running in the environment by reviewing installed software, running services, or web server configurations pointing to Devolutions web portals.
    Affected if Devolutions Server is installed and serving HTTP responses.
  2. Check installed version
    Locate the installed Devolutions Server version through the application's About page, admin console, or installed programs list on the server.
    Affected if The version is lower than 2023.3.8.0 (any version from 2023.3.7.0 and earlier).
  3. Inspect HTTP response headers
    Send an HTTP request to the Devolutions Server web interface and capture the response headers, specifically looking for the Content-Security-Policy header.
    Affected if The server returns a Content-Security-Policy header in HTTP responses.
  4. Analyze CSP header for sensitive endpoints
    Examine the full Content-Security-Policy header value for any URI references that reveal internal Devolutions Gateway endpoint configurations, such as internal hostnames, IP addresses, or specific gateway paths.
    Affected if The CSP header contains URI values that expose internal or private Devolutions Gateway endpoint addresses or paths.

A user is affected if they are running Devolutions Server version 2023.3.7.0 or earlier and the HTTP responses include a Content-Security-Policy header that reveals internal gateway endpoint configurations.

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.3.8.0 or later
Fixed in 2023.3.8.0
Interim mitigation

Update Devolutions Server to version 2023.3.8.0 or later which contains the security fix, or configure the web server to strip or sanitize sensitive information from the Content-Security-Policy header before serving responses.

Recommended fix Moderate confidence

2023.3.8.0

  1. Upgrade Devolutions Server to version 2023.3.8.0 or later to remediate the Content-Security-Policy information exposure vulnerability
  2. After upgrading, verify the Content-Security-Policy header no longer leaks gateway endpoint information
  3. Confirm the upgrade was successful by reviewing the server configuration

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Devolutions Server Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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