dbcve.org
Octopus ServerApplication · Octopus

CVE-2022-2721

HIGH · 7.5 CVSS v3.1 Published 2022-11-25
Fix available
A fix is available. Upgrade to 2022.2.7965 / 2022.3.9163 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 target discovery to print certain values marked as sensitive to log files in plaint-text in when verbose logging is enabled.

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 Octopus Server versions, target discovery writes certain values marked as sensitive to log files in plain-text when verbose logging is enabled. This exposes credentials, tokens, or other secrets that should be redacted, leading to information disclosure.

MitigationDisable verbose logging in Octopus Server or upgrade to a patched version that properly redacts sensitive values in logs.

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.2.6729, < 2022.2.7965>= 2022.3.348, < 2022.3.9163

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. Check installed Octopus Server version
    Navigate to the Octopus Web Portal, click Help > About, or run 'octo version' from the command line to retrieve the exact version number
    Affected if The installed version falls within 2022.2.6729 to 2022.2.7965, or 2022.3.348 to 2022.3.9163
  2. Verify if verbose logging is enabled
    In the Octopus Web Portal, go to Configuration > Diagnostics > Log Settings, or inspect the configuration file where logging levels are defined. Look for a verbose or debug logging level being active.
    Affected if Verbose or debug logging is enabled on the Octopus Server instance
  3. Determine if target discovery has been performed
    In the Octopus Web Portal, check the Infrastructure > Deployment Targets or Targets page for any recently discovered or added targets, or review recent deployment target creation events.
    Affected if Any deployment targets have been discovered or added since the vulnerable version was installed
  4. Examine log files for sensitive values in plain text
    Locate and review the Octopus Server log files (typically found in the Logs folder of the Octopus installation directory). Search for credential-like strings, tokens, or API keys that appear in plain text rather than being masked or redacted.
    Affected if Log files contain unmasked credentials, tokens, or secrets that should have been redacted

A user is affected if they are running a vulnerable Octopus Server version (2022.2.6729-2022.2.7965 or 2022.3.348-2022.3.9163), have verbose logging enabled, and have performed target discovery operations that may have exposed sensitive values 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 2022.2.7965 / 2022.3.9163 or later
Fixed in 2022.2.79652022.3.9163
Interim mitigation

Disable verbose logging in Octopus Server or upgrade to a patched version that properly redacts sensitive values in logs.

Recommended fix High confidence

Upgrade to Octopus Server 2022.2.7965 (for 2022.2.x line) or 2022.3.9163 (for 2022.3.x line) or later

  1. Identify your current Octopus Server version by checking the web UI or running `octopus version`
  2. Backup your Octopus Server database and configuration files
  3. For versions 2022.2.x: Upgrade to version 2022.2.7965 or later
  4. For versions 2022.3.x: Upgrade to version 2022.3.9163 or later
  5. Download the installer from the Octopus downloads page
  6. Stop the Octopus Server service
  7. Run the installer and follow the upgrade prompts
  8. Start the Octopus Server service and verify the upgrade was successful

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-2022-2721 — 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-2721 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