dbcve.org
Octopus ServerApplication · Octopus

CVE-2022-2781

MEDIUM · 5.3 CVSS v3.1 Published 2022-10-06
Fix available
A fix is available. Upgrade to 2022.1.3154 / 2022.2.7897 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 Server it was identified that the same encryption process was used for both encrypting session cookies and variables.

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 used identical encryption mechanisms for securing session cookies and sensitive variables, creating a cryptographic weakness where compromise of one encryption pathway could potentially expose the other.

MitigationReview and implement separate, purpose-specific encryption processes for session cookies versus variables, using distinct keys and appropriate algorithms for each data sensitivity level.

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.2.10, < 2022.1.3154>= 2022.2.6729, < 2022.2.7897>= 2022.3.348, < 2022.3.10586

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 installed Octopus Server version
    Navigate to Configuration > About in the Octopus Web UI, or run 'octopus.server --version' from the server installation directory
    Affected if The version falls within >= 3.2.10 and < 2022.1.3154, OR >= 2022.2.6729 and < 2022.2.7897, OR >= 2022.3.348 and < 2022.3.10586
  2. Confirm Octopus Server is operational and accepting connections
    Verify the web interface is accessible and the server service is running via Services.msc or 'sc query OctopusDeploy'
    Affected if The server is running and accessible, enabling the vulnerable encryption pathway to be exercised
  3. Determine if sensitive variables are configured
    In the Octopus Web UI, navigate to Library > Variable Sets and review any variable sets for sensitive (masked) variables
    Affected if Sensitive variables exist in any library variable set or project variable scope
  4. Verify session-based authentication is in use
    Confirm users access the Octopus Web UI via browser session cookies rather than API keys only
    Affected if User authentication uses web session cookies (the primary authentication method for the UI)

You are affected if your installed version is within any of the three vulnerable ranges AND the server handles both web session cookies and sensitive variables using the default identical encryption mechanism.

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.1.3154 / 2022.2.7897 / 2022.3.10586 or later
Fixed in 2022.1.31542022.2.78972022.3.10586
Interim mitigation

Review and implement separate, purpose-specific encryption processes for session cookies versus variables, using distinct keys and appropriate algorithms for each data sensitivity level.

Recommended fix High confidence

Upgrade to 2022.1.3154+ (if on 3.2.10-2022.1.x), or 2022.2.7897+ (if on 2022.2.x), or 2022.3.10586+ (if on 2022.3.x)

  1. 1. Identify current Octopus Server version by navigating to the Octopus Web Portal and checking the version in the footer, or by running 'Octopus.Server version' from the command line
  2. 2. Based on current version, determine the appropriate upgrade path: if currently on 3.2.10 through 2022.1.x, plan upgrade to 2022.1.3154 or later; if on 2022.2.x, plan upgrade to 2022.2.7897 or later; if on 2022.3.x, plan upgrade to 2022.3.10586 or later
  3. 3. Before upgrading, perform a full backup of the Octopus database and configuration
  4. 4. Download the appropriate fixed version of Octopus Server from the official downloads page
  5. 5. Run the installer or follow upgrade instructions to apply the new version
  6. 6. After upgrade, verify the server is running correctly and test that encrypted variables and session cookies function properly
Caveat Review Octopus Server release notes for the target version to check for any breaking changes between current and target versions, particularly around encryption or configuration settings

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

Fix this in Octopus Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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