dbcve.org
Octopus ServerApplication · Octopus

CVE-2022-2720

MEDIUM · 5.3 CVSS v3.1 Published 2022-10-12
Fix available
A fix is available. Upgrade to 2022.1.3154 / 2022.2.7934 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
In affected versions of Octopus Server it was identified that when a sensitive value is a substring of another value, sensitive value masking will only partially work.

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 confidence

In Octopus Server, sensitive value masking fails to fully protect sensitive data when that sensitive value (e.g., a password) appears as a substring within another value. This partial masking failure could allow attackers or unauthorized users to view portions of sensitive data in logs or output.

MitigationUpgrade to a patched version of Octopus Server that properly handles substring scenarios in sensitive value masking, or review and restrict access to any logs/output that may contain partially masked values.

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:>= 3.16.4, < 2022.1.3154>= 2022.2.6729, < 2022.2.7934>= 2022.3.348, < 2022.3.10586

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. Determine Octopus Server version
    Navigate to the Octopus Web UI, go to Configuration > About, or check the installation directory for version information
    Affected if The installed version falls within one of these ranges: >= 3.16.4 and < 2022.1.3154, OR >= 2022.2.6729 and < 2022.2.7934, OR >= 2022.3.348 and < 2022.3.10586
  2. Identify sensitive variables in use
    In the Octopus Web UI, navigate to Variables > Library Variable Sets, or check your deployment processes for variables marked as sensitive (such as passwords, API keys, connection strings)
    Affected if Sensitive variables are configured and the server version is in the affected ranges
  3. Review task logs for masking behavior
    Run a deployment or execute a process that uses sensitive variables, then navigate to Tasks > [task name] > Output and inspect the raw logs
    Affected if Logs show partially masked values where a sensitive value appears as a substring within a longer string (e.g., a password 'abc123' appearing within a connection string shows as '***bc123' instead of full masking)
  4. Check API and raw output endpoints
    Use the Octopus API or export deployment scripts/processes to raw output and inspect for sensitive values
    Affected if Raw output or API responses contain partial representations of sensitive data that should be fully masked

You are affected if you are running any Octopus Server version within the affected ranges AND you use sensitive variables that could appear as substrings in logs or output.

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 2022.1.3154 / 2022.2.7934 / 2022.3.10586 or later
Fixed in 2022.1.31542022.2.79342022.3.10586
Interim mitigation

Upgrade to a patched version of Octopus Server that properly handles substring scenarios in sensitive value masking, or review and restrict access to any logs/output that may contain partially masked values.

Recommended fix High confidence

2022.1.3154 (or later in 2022.1.x), 2022.2.7934 (or later in 2022.2.x), or 2022.3.10586 (or later in 2022.3.x) depending on your current release line

  1. Identify which version range your current Octopus Server installation falls within (3.16.4 to 2022.1.3153, 2022.2.6729 to 2022.2.7933, or 2022.3.348 to 2022.3.10585)
  2. Ensure you have a valid backup of your Octopus Server database and configuration
  3. Review the Octopus Server upgrade guide at https://octopus.com/docs/administration/upgrading
  4. For version range 3.16.4 to 2022.1.x: upgrade to version 2022.1.3154 or later
  5. For version range 2022.2.6729 to 2022.2.x: upgrade to version 2022.2.7934 or later
  6. For version range 2022.3.348 to 2022.3.x: upgrade to version 2022.3.10586 or later
  7. Perform the upgrade following standard Octopus Server upgrade procedures
  8. Verify that sensitive value masking now correctly handles substring matches
Caveat Standard Octopus upgrade considerations apply; review release notes for your target version for any deprecated features or migration requirements

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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