dbcve.org
Octopus ServerApplication · Octopus

CVE-2022-3614

MEDIUM · 6.1 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 →
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 versions of Octopus Deploy users of certain browsers using AD to sign-in to Octopus Server were able to bypass authentication checks and be redirected to the configured redirect url without any validation.

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, users authenticating via Active Directory in certain browsers could bypass authentication checks and be redirected to a configured redirect URL without proper validation, potentially allowing unauthorized access to the application.

MitigationApply the vendor patch for this authentication bypass vulnerability. Until patched, review and restrict configured redirect URLs and monitor for unauthorized access attempts.

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.5, < 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
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. Identify installed Octopus Server version
    Navigate to the Octopus Web Portal, click your profile icon, select 'About' to view the version number, or check the installation directory for version information
    Affected if The installed version falls within >= 3.5, < 2022.3.10750 OR >= 2022.4, < 2022.4.8063
  2. Verify Active Directory authentication is configured
    In Octopus Deploy, go to Configuration > Authentication Providers and confirm the 'Active Directory' or 'Active Directory Integrated' provider is enabled
    Affected if Active Directory authentication provider is enabled and in use
  3. Examine configured redirect URLs
    In the Active Directory authentication settings, review any configured 'Redirect URL' or 'Post-login redirect' fields that control where users are sent after authenticating
    Affected if Any redirect URLs are configured in the Active Directory authentication settings (the vulnerability allows bypassing validation of these URLs)

Your environment is affected if you are running a vulnerable Octopus Server version (within the specified ranges) AND have Active Directory authentication enabled with configured redirect URLs.

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

Apply the vendor patch for this authentication bypass vulnerability. Until patched, review and restrict configured redirect URLs and monitor for unauthorized access attempts.

Recommended fix High confidence

Octopus Server 2022.3.10750 or 2022.4.8063 (depending on your current major/minor version)

  1. Identify the current Octopus Server version from the UI or command line (Help > About)
  2. Review the upgrade path: if currently on 2022.3.x, upgrade to 2022.3.10750 or later; if on 2022.4.x, upgrade to 2022.4.8063 or later
  3. Take a backup of the Octopus database and configuration files before upgrading
  4. Download the target fixed version from downloads.octopus.com
  5. Stop the Octopus Server service
  6. Install the new version using the installer or perform a rolling upgrade following Octopus documentation
  7. Start the Octopus Server service
  8. Verify the fix by testing the AD authentication redirect flow in affected browsers to confirm proper validation is applied

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
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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