dbcve.org
Octopus DeployApplication · Octopus

CVE-2023-2247

MEDIUM · 5.3 CVSS v3.1 Published 2023-05-02
Fix available
A fix is available. Upgrade to 2022.3.10929 / 2022.4.8319 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 Deploy it is possible to unmask variable secrets using the variable preview function

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 affected versions of Octopus Deploy, the variable preview function contains an information disclosure vulnerability that allows users to unmask variable secrets that should remain hidden. This exposes sensitive credentials, API keys, passwords, and other secrets that were intended to be masked in the deployment system.

MitigationUpgrade to a patched version of Octopus Deploy when available, and review access controls to ensure only authorized personnel can access variable preview functionality.

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 DeployApplication
Affected:>= 2018.3.0, < 2022.3.10929>= 2022.4.0, < 2022.4.8319

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. Identify the installed Octopus Deploy version
    Log into the Octopus Web UI, click your username in the top-right corner, and view the version number displayed in the footer or in the System node under About. Alternatively, check the server startup logs or the installation directory for version metadata.
    Affected if The installed version falls within 2018.3.0 to 2022.3.10928 (exclusive of 2022.3.10929) OR within 2022.4.0 to 2022.4.8318 (exclusive of 2022.4.8319).
  2. Verify the variable preview feature is accessible
    Navigate to any project in Octopus Deploy that contains deployment or runbook processes. Locate a step that uses variables, and access the variable preview or variable debugging interface available during process editing or release creation.
    Affected if The variable preview interface loads and displays variable values without requiring elevated permissions beyond standard user access.
  3. Confirm sensitive variables exist in the deployment configuration
    Review one or more projects in the Octopus library under Variables or in the release creation step. Identify if any variables are marked as sensitive, scoped to environments, or intended to hold credentials, API keys, or secrets.
    Affected if Sensitive-type variables, scoped secrets, or variables explicitly meant to be masked are present in the system.
  4. Test whether unmasking occurs in variable preview
    As a non-administrator or standard user with access to a project containing masked variables, open the variable preview for a release or deployment process. Observe whether previously masked variable values become visible in plaintext.
    Affected if Variable secrets that were configured to be masked appear in plaintext or unmasked form within the preview interface.

A user is affected if their Octopus Deploy version is within the vulnerable ranges AND they have access to the variable preview feature with sensitive variables configured in the system.

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.10929 / 2022.4.8319 or later
Fixed in 2022.3.109292022.4.8319
Interim mitigation

Upgrade to a patched version of Octopus Deploy when available, and review access controls to ensure only authorized personnel can access variable preview functionality.

Recommended fix High confidence

2022.3.10929 (or later 2022.3.x) or 2022.4.8319 (or later 2022.4.x); prefer latest stable 2022.x release

  1. Identify your current Octopus Deploy version by checking the server's About page
  2. Determine which upgrade path applies: if on 2022.3.x line, upgrade to >=2022.3.10929; if on 2022.4.x line, upgrade to >=2022.4.8319
  3. Review the Octopus Deploy release notes for the target version to understand any pre-upgrade requirements
  4. Ensure you have a current backup of your Octopus database and configuration
  5. Stop the Octopus Server service before upgrading
  6. Download the appropriate installer from the Octopus Deploy downloads page
  7. Run the installer and follow the upgrade wizard prompts
  8. Restart the Octopus Server service after upgrade completes
Caveat Minor version upgrades typically have no breaking changes, but review release notes for any configuration or feature deprecations

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

Fix this in Octopus Deploy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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