dbcve.org
Octopus DeployApplication · Octopus

CVE-2022-23184

MEDIUM · 6.1 CVSS v3.1 Published 2022-02-07
Fix available
A fix is available. Upgrade to 2021.2.8011 / 2021.3.11057 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Octopus Server versions when the server HTTP and HTTPS bindings are configured to localhost, Octopus Server will allow open redirects.

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

Octopus Server versions with HTTP/HTTPS bindings configured to localhost are vulnerable to open redirect attacks. The server improperly validates redirect URLs, allowing attackers to craft malicious links that redirect users to arbitrary external sites while appearing to originate from the legitimate Octopus Server domain.

MitigationAvoid configuring Octopus Server HTTP/HTTPS bindings to localhost in production environments, or apply vendor-supplied patches when available. Validate that all redirect destinations are within expected domains.

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:>= 0.9, <= 4.1.10>= 2018.1.0, <= 2020.1.1
Octopus ServerApplication
Affected:>= 2021.2.0, < 2021.2.8011>= 2021.3.0, < 2021.3.11057

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 installed Octopus Server version
    Run 'octopus.server --version' or check the server's About page in the web UI
    Affected if Version falls within >= 0.9 to <= 4.1.10, >= 2018.1.0 to <= 2020.1.1, >= 2021.2.0 to < 2021.2.8011, or >= 2021.3.0 to < 2021.3.11057
  2. Locate server configuration file
    Find the Octopus server configuration file (commonly in the instance directory or /etc/octopus)
    Affected if Configuration file exists and contains server binding settings
  3. Inspect HTTP/HTTPS binding settings
    Open the configuration file and locate the server binding or URL settings
    Affected if Bindings are configured to use 'localhost', '127.0.0.1', or any loopback address for HTTP/HTTPS endpoints
  4. Verify network exposure
    Check if the server is accessible from external networks or if port 80/443 is exposed publicly
    Affected if The localhost-bound server is accessible to external clients or the port is exposed beyond the local machine

You are affected if your Octopus Server version matches the affected ranges AND HTTP/HTTPS bindings are configured to localhost with external accessibility possible.

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 2021.2.8011 / 2021.3.11057 or later
Fixed in 2021.2.80112021.3.11057
Interim mitigation

Avoid configuring Octopus Server HTTP/HTTPS bindings to localhost in production environments, or apply vendor-supplied patches when available. Validate that all redirect destinations are within expected domains.

Recommended fix High confidence

2021.2.8011 or later for 2021.2.x; 2021.3.11057 or later for 2021.3.x; latest current stable release recommended

  1. 1. Identify your current Octopus Server/Deploy version by checking the server's About page or using the API endpoint /api/about
  2. 2. For Octopus Server 2021.2.x users: Upgrade to version 2021.2.8011 or later
  3. 3. For Octopus Server 2021.3.x users: Upgrade to version 2021.3.11057 or later
  4. 4. For Octopus Deploy 4.1.x users: Upgrade to version 4.1.11 or later (if available)
  5. 5. For Octopus Deploy 2020.1.x users: Upgrade to version 2020.1.2 or later (if available)
  6. 6. After upgrade, verify the open redirect vulnerability is resolved by testing with a crafted URL containing an external redirect
  7. 7. Review server logs to confirm no unauthorized redirects have occurred
Caveat Review release notes for your target version for any configuration or migration considerations

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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