dbcve.org
Octopus ServerApplication · Octopus

CVE-2022-4008

MEDIUM · 5.5 CVSS v3.1 Published 2023-05-10
Fix available
A fix is available. Upgrade to 2022.3.11043 / 2022.4.8401 or later.
See remediation →
58/100
Remediation priority · Elevated
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 it is possible to upload a zipbomb file as a task which results in Denial of Service

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 Deploy does not properly validate uploaded task files, allowing attackers to upload zipbomb archives that decompress to extreme sizes causing resource exhaustion and denial of service.

MitigationImplement file size limits both before and after decompression, add zipbomb detection logic, restrict accepted archive types, and update to patched version when available.

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:>= 0.9, < 2022.3.11043>= 2022.4.791, < 2022.4.8401

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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. Identify installed Octopus Server version
    Check the version via the web UI (Help > About), or check the installation directory for a version file, or run 'octo version' if the CLI is available
    Affected if The version falls within < 2022.3.11043 or >= 2022.4.791 and < 2022.4.8401
  2. Determine if task file uploads are accepted
    Review whether deployments, script tasks, or package imports accept ZIP archives or compressed files from users or external systems
    Affected if The server accepts ZIP archives as part of deployment tasks or script execution
  3. Check for existing archive size limits
    Inspect Octopus configuration files (octopus.config or deployment settings) for MaxUploadSize, MaxPackageSize, or similar decompression limits
    Affected if No limits are configured for uploaded archive sizes before or after decompression
  4. Verify if external users can submit tasks
    Review authentication settings and determine if unauthenticated or low-privilege users can trigger deployments or upload task-related files
    Affected if Unauthenticated or low-privileged users can trigger deployments that accept archive uploads

You are affected if your Octopus Server version is less than 2022.3.11043 or between 2022.4.791 and 2022.4.8401 AND your deployment tasks accept ZIP archives from users or external sources.

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.11043 / 2022.4.8401 or later
Fixed in 2022.3.110432022.4.8401
Interim mitigation

Implement file size limits both before and after decompression, add zipbomb detection logic, restrict accepted archive types, and update to patched version when available.

Recommended fix High confidence

Upgrade to Octopus Server 2022.3.11043 or later (for 2022.3.x line) OR 2022.4.8401 or later (for 2022.4.x line)

  1. 1. Identify current Octopus Server version from the Admin > Diagnostics page
  2. 2. For versions >= 0.9 and < 2022.3.11043: Plan upgrade to version 2022.3.11043 or later
  3. 3. For versions >= 2022.4.791 and < 2022.4.8401: Plan upgrade to version 2022.4.8401 or later
  4. 4. Review Octopus Deploy release notes for the target version for any breaking changes
  5. 5. Perform a full backup of the Octopus database and configuration before upgrading
  6. 6. Test the upgrade in a non-production environment first
  7. 7. Execute the upgrade following standard Octopus Server upgrade procedures
  8. 8. Verify the upgrade was successful and the zipbomb vulnerability is resolved
Caveat Review Octopus Deploy release notes for the target version for any configuration or feature changes that may affect your deployment

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-4008 — 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-4008 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