dbcve.org
Octopus ServerApplication · Octopus

CVE-2022-3460

HIGH · 7.5 CVSS v3.1 Published 2023-01-03
Fix available
A fix is available. Upgrade to 2022.3.10750 / 2022.4.8063 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 Deploy it is possible for certain types of sensitive variables to inadvertently become unmasked when viewed in variable preview.

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

A vulnerability in Octopus Deploy's variable preview feature allows sensitive variables to be displayed in plaintext instead of being properly masked, exposing secrets such as API keys, passwords, or other credentials to users who view the variable preview.

MitigationRestrict access to variable preview functionality pending a patch; review access logs for unauthorized access to sensitive variables; rotate any credentials that may have been exposed through this vulnerability.

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.1.0, < 2022.3.10750>= 2022.4, < 2022.4.8063

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
    Locate the Octopus Server version in the web UI (typically in the footer or under System > About) or via the API endpoint /api/system/health
    Affected if The installed version falls within >= 2018.1.0 and < 2022.3.10750, OR >= 2022.4 and < 2022.4.8063
  2. Identify if variable preview functionality is accessible
    Determine whether users have access to the variable preview feature in projects - this feature allows viewing variable values during deployment or release creation screens
    Affected if Any users with access to projects can view the variable preview and sensitive variables are displayed unmasked in the UI
  3. Review audit logs for variable preview access
    Check Octopus audit logs (under Audit section in the UI) for entries related to variable preview or sensitive variable access, particularly from users who should not have plaintext visibility into secrets
    Affected if Audit logs show unauthorized or unexpected access to sensitive variable values through the preview feature
  4. Inspect variable configurations for sensitive types
    Review your Octopus variable sets to identify variables marked as sensitive (API keys, passwords, tokens) - these should normally be masked but may be exposed via the preview flaw
    Affected if Sensitive-type variables exist in your deployment processes and the server version is within the affected range

You are affected if your Octopus Server version falls within the vulnerable ranges and users have access to the variable preview feature where sensitive variables could be displayed in plaintext.

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.3.10750 / 2022.4.8063 or later
Fixed in 2022.3.107502022.4.8063
Interim mitigation

Restrict access to variable preview functionality pending a patch; review access logs for unauthorized access to sensitive variables; rotate any credentials that may have been exposed through this vulnerability.

Recommended fix Moderate confidence

Upgrade to 2022.3.10750 or later (for 2022.3.x branch) or 2022.4.8063 or later (for 2022.4.x branch)

  1. Determine your current Octopus Server version from the System node in the web interface
  2. If running version >= 2018.1.0 and < 2022.3.10750, upgrade to version 2022.3.10750 or later
  3. If running version >= 2022.4 and < 2022.4.8063, upgrade to version 2022.4.8063 or later
  4. After upgrade, verify that sensitive variables remain masked in variable preview functionality

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

Fix this in Octopus Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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