dbcve.org
Octopus ServerApplication · Octopus

CVE-2022-2782

CRITICAL · 9.1 CVSS v3.1 Published 2022-10-27
Fix available
A fix is available. Upgrade to 2022.2.8351 / 2022.3.10586 or later.
See remediation →
100/100
Remediation priority · Urgent
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 a session token to be valid indefinitely due to improper validation of the session token parameters.

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 affected have a session token validation flaw where tokens can remain valid indefinitely due to improper validation of session token parameters, allowing attackers with compromised or intercepted tokens to maintain persistent access.

MitigationUpgrade to a patched version of Octopus Server and rotate all existing session tokens to invalidate any potentially compromised sessions.

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.8351>= 2022.3.0, < 2022.3.10586>= 2022.4.0, < 2022.4.2898

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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
    Log into the Octopus Web UI and navigate to the Configuration > Nodes page, or run 'octo version' via the command line if the Octopus CLI is installed
    Affected if The displayed version matches any of the affected ranges: < 2022.2.8351, >= 2022.3.0 and < 2022.3.10586, or >= 2022.4.0 and < 2022.4.2898
  2. Check server startup logs for version confirmation
    Review the Octopus Server logs (typically found in the logs directory of the Octopus installation) for the startup entry showing the exact version number
    Affected if The logged version falls within the affected ranges listed above
  3. Review active session audit logs
    In the Octopus Web UI, go to Configuration > Audit to search for session-related events such as 'User logged in' or 'Session created' entries
    Affected if Session entries exist from dates prior to applying a patched version, indicating tokens may still be valid
  4. Compare current version to patched releases
    Refer to Octopus Deploy release notes or vendor documentation to confirm what version you are running versus the fixed versions (2022.2.8351, 2022.3.10586, or 2022.4.2898 and later)
    Affected if Your installed version is lower than any of these patched versions

You are affected if your Octopus Server version falls within the listed affected ranges AND you have not rotated session tokens since the vulnerability period.

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.8351 / 2022.3.10586 / 2022.4.2898 or later
Fixed in 2022.2.83512022.3.105862022.4.2898
Interim mitigation

Upgrade to a patched version of Octopus Server and rotate all existing session tokens to invalidate any potentially compromised sessions.

Recommended fix High confidence

2022.2.8351 (or 2022.3.10586 or 2022.4.2898 depending on your current branch)

  1. 1. Backup your Octopus Server database and configuration
  2. 2. Download the appropriate fixed version of Octopus Server for your current release line
  3. 3. If running Octopus Server 2022.1.x or earlier, upgrade to 2022.2.8351 or later
  4. 4. If running Octopus Server 2022.3.x, upgrade to 2022.3.10586 or later
  5. 5. If running Octopus Server 2022.4.x, upgrade to 2022.4.2898 or later
  6. 6. Run the upgrade installer on your Octopus Server instance
  7. 7. Verify that existing sessions work correctly after the upgrade
  8. 8. Confirm session tokens now properly expire according to configuration
Caveat Minor patch upgrades typically have low risk; review Octopus release notes for any deprecation notices

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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