dbcve.org
Octopus ServerApplication · Octopus

CVE-2021-31820

HIGH · 7.5 CVSS v3.1 Published 2021-08-18
Fix available
A fix is available. Upgrade to 2020.6.5310 / 2021.1.7622 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 Octopus Server after version 2018.8.2 if the Octopus Server Web Request Proxy is configured with authentication, the password is shown in plaintext in the UI.

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 Octopus Server versions after 2018.8.2, when the Web Request Proxy is configured with authentication credentials, the password is displayed in plaintext in the user interface instead of being masked or hidden, allowing unauthorized users with UI access to view sensitive authentication credentials.

MitigationAvoid configuring proxy authentication until the vendor patch is applied; alternatively, ensure only trusted administrators have access to the Octopus Server administration UI where proxy settings are displayed.

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:> 2018.8.2, < 2020.6.5310>= 2021.1.0, < 2021.1.7622

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. Identify Octopus Server version
    Check the Octopus Server installation for its version number, typically found in the UI under 'Configuration' > 'About' or via the server's startup logs
    Affected if The installed version falls within > 2018.8.2 and < 2020.6.5310, OR >= 2021.1.0 and < 2021.1.7622
  2. Confirm Web Request Proxy is configured
    Navigate to the Octopus Server administration UI and locate the Web Request Proxy settings, typically under 'Configuration' > 'System' > 'Proxy' or 'Infrastructure' > 'Proxy'
    Affected if A proxy server is configured and the settings page is accessible in the UI
  3. Verify proxy authentication is enabled
    In the Web Request Proxy settings, check whether authentication credentials (username/password) are configured for the proxy connection
    Affected if Authentication credentials are set for the proxy (username field is populated)
  4. Check if password is visible in plaintext
    In the Web Request Proxy settings UI, observe whether the password field displays plaintext characters or is properly masked/hidden
    Affected if The password field shows plaintext characters instead of being masked with dots or asterisks

You are affected if you run an Octopus Server version in the affected ranges AND have Web Request Proxy configured with authentication credentials visible in plaintext in the UI.

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 2020.6.5310 / 2021.1.7622 or later
Fixed in 2020.6.53102021.1.7622
Interim mitigation

Avoid configuring proxy authentication until the vendor patch is applied; alternatively, ensure only trusted administrators have access to the Octopus Server administration UI where proxy settings are displayed.

Recommended fix High confidence

Upgrade to 2020.6.5310+ (2020 LTS recommended) or 2021.1.7622+ (2021.2+ recommended)

  1. 1. Determine your current Octopus Server version from the UI (top-right corner) or using the API endpoint /api/status
  2. 2. For version 2020.x: Upgrade to version 2020.6.5310 or later (recommended: latest 2020 LTS)
  3. 3. For version 2021.1.x: Upgrade to version 2021.1.7622 or later (recommended: latest 2021.1.x or 2021.2+)
  4. 4. Before upgrading, backup your Octopus Server database and configuration
  5. 5. Follow standard Octopus Server upgrade procedure: download installer from octopus.com/downloads, stop the Octopus service, run the installer, and follow prompts
  6. 6. After upgrade, verify the Web Request Proxy settings no longer display plaintext passwords in the UI
Caveat Standard upgrade risks apply - test in staging first; review release notes for any breaking changes between your version and target

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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