dbcve.org
Octopus ServerApplication · Octopus

CVE-2022-4009

HIGH · 8.8 CVSS v3.1 Published 2023-03-16
Fix available
A fix is available. Upgrade to 2022.2.8552 / 2022.3.10750 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 for a user to introduce code via offline package creation

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, an authenticated user can introduce arbitrary code during offline package creation. This allows malicious code to be embedded in deployment packages, potentially leading to supply chain attacks when those packages are deployed to target environments.

MitigationUpdate Octopus Deploy to the patched version. Audit existing offline packages for malicious content and implement additional validation/sanitization for package contents during offline creation workflows.

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.0.19, < 2022.2.8552>= 2022.3.348, < 2022.3.10750>= 2022.4.791, < 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Check installed Octopus Server version
    Navigate to the Octopus Web Portal, click your profile icon in the top right, and select 'About'. The version number is displayed on the 'Octopus Server' line. Alternatively, check the Windows installed programs list or the Octopus Server logs.
    Affected if The installed version is >= 3.0.19 AND < 2022.2.8552, OR >= 2022.3.348 AND < 2022.3.10750, OR >= 2022.4.791 AND < 2022.4.8319
  2. Confirm offline package creation feature usage
    Review Octopus deployment processes and runbooks for any steps that create offline packages. Check API access logs for calls to endpoints related to offline package creation, such as /api/packages/offline or similar package upload endpoints.
    Affected if The Octopus Server environment uses or has used offline package creation functionality at any point while running an affected version
  3. Identify users with package creation permissions
    In the Octopus Web Portal, go to 'Users' and 'Teams' sections. Review user roles and permissions to determine which accounts have package creation, package upload, or process editing rights.
    Affected if There are user accounts with permissions to create or upload packages, particularly non-administrator accounts in affected versions

You are affected if your Octopus Server version falls within any of the three affected ranges AND your environment has used offline package creation with authenticated user accounts that have package creation permissions.

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.8552 / 2022.3.10750 / 2022.4.8319 or later
Fixed in 2022.2.85522022.3.107502022.4.8319
Interim mitigation

Update Octopus Deploy to the patched version. Audit existing offline packages for malicious content and implement additional validation/sanitization for package contents during offline creation workflows.

Recommended fix High confidence

Upgrade to 2022.2.8552 (or later 2022.2.x), 2022.3.10750 (or later 2022.3.x), or 2022.4.8319 (or later 2022.4.x) depending on your current branch

  1. 1. Identify the currently installed Octopus Server version from the UI (Configuration > Nodes) or via the API
  2. 2. Determine which version branch your current installation falls into (2022.2.x, 2022.3.x, or 2022.4.x)
  3. 3. For 2022.2.x line: upgrade to version 2022.2.8552 or later
  4. 4. For 2022.3.x line: upgrade to version 2022.3.10750 or later
  5. 5. For 2022.4.x line: upgrade to version 2022.4.8319 or later
  6. 6. Review Octopus Deploy release notes for your target version to understand any required migration steps
  7. 7. Perform a backup of the Octopus database and configuration before upgrading
  8. 8. Test the upgrade in a non-production environment first
Caveat Review Octopus Deploy release notes for the target version for any breaking changes or required migration steps; major version jumps may require additional consideration

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

Fix this in Octopus Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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