dbcve.org
Octopus ServerApplication · Octopus

CVE-2023-1904

HIGH · 7.5 CVSS v3.1 Published 2023-12-14
Fix available
A fix is available. Upgrade to 2023.1.11942 / 2023.2.13151 or later.
See remediation →
84/100
Remediation priority · High
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
In affected versions of Octopus Server it is possible for the OpenID client secret to be logged in clear text during the configuration of Octopus Server.

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

In affected versions of Octopus Server, the OpenID client secret is logged in clear text during server configuration. This is an information disclosure vulnerability where sensitive authentication credentials are written to logs without encryption, potentially exposing them to attackers with log access.

MitigationImmediately rotate any exposed OpenID client secrets and update Octopus Server to the patched version. Review log files for any unauthorized access to the plaintext credentials.

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
Octopus ServerApplication
Affected:>= 2022.1.2121, < 2023.1.11942>= 2023.2.2028, < 2023.2.13151>= 2023.3.317, < 2023.3.5049

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Determine installed Octopus Server version
    Access the Octopus Server UI and navigate to Configuration > About, or query the API endpoint /api/system/health or check the installer/environment documentation for the running instance
    Affected if The installed version falls within any of these ranges: >= 2022.1.2121 and < 2023.1.11942, OR >= 2023.2.2028 and < 2023.2.13151, OR >= 2023.3.317 and < 2023.3.5049
  2. Verify OpenID Connect authentication is configured
    Navigate to Configuration > Authentication Providers in the Octopus UI and confirm an OpenID Connect provider is enabled with a client secret configured
    Affected if OpenID Connect authentication is enabled with a client secret set in the server configuration
  3. Examine server logs for plaintext credentials
    Search the Octopus Server log files for the configured OpenID client secret value, looking in the deployment logs and configuration logs directory
    Affected if The OpenID client secret appears in any log file in cleartext form

A user is affected if their Octopus Server version is within the affected ranges AND they have OpenID authentication configured, with the client secret appearing in plaintext in logs.

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.1.11942 / 2023.2.13151 / 2023.3.5049 or later
Fixed in 2023.1.119422023.2.131512023.3.5049
Interim mitigation

Immediately rotate any exposed OpenID client secrets and update Octopus Server to the patched version. Review log files for any unauthorized access to the plaintext credentials.

Recommended fix High confidence

Upgrade to the minimum fixed version for your branch: 2023.1.11942 (if on 2022.1.x), 2023.2.13151 (if on 2023.2.x), or 2023.3.5049 (if on 2023.3.x) - preferably upgrade to the latest stable release in your branch

  1. 1. Identify your current Octopus Server version via the UI (Configuration -> Nodes) or via the API endpoint /api/serverstatus
  2. 2. Based on your current version, determine your upgrade path: if you are on 2022.1.x (>= 2022.1.2121), upgrade to 2023.1.11942 or later; if you are on 2023.2.x (>= 2023.2.2028), upgrade to 2023.2.13151 or later; if you are on 2023.3.x (>= 2023.3.317), upgrade to 2023.3.5049 or later
  3. 3. Before upgrading, perform a full backup of your Octopus Server database and configuration - refer to official documentation for backup procedures
  4. 4. Download the appropriate installer for your target version from downloads.octopus.com
  5. 5. Run the installer to upgrade your Octopus Server instance
  6. 6. After upgrade, verify the OpenID configuration no longer logs the client secret in clear text by reviewing logs during an Octopus restart or OpenID reconfiguration
Caveat Review Octopus Server release notes for your target version for any breaking changes or migration requirements between major versions

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

Fix this in Octopus Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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