dbcve.org
Octopus ServerApplication · Octopus

CVE-2022-2528

MEDIUM · 6.5 CVSS v3.1 Published 2022-09-09
Fix available
A fix is available. Upgrade to 2022.1.3106 / 2022.2.7718 or later.
See remediation →
71/100
Remediation priority · Elevated
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 to upload a package to built-in feed with insufficient permissions after re-indexing packages.

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, a permission bypass exists in the built-in package feed where users with insufficient permissions can upload packages after the package re-indexing process occurs. The re-indexing operation appears to reset or fail to properly enforce authorization controls, allowing unauthorized package uploads.

MitigationUpgrade Octopus Deploy to the patched version as specified in the vendor advisory. Review user role assignments and package feed permissions as part of remediation testing.

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.0, <= 4.1.10>= 2018.1.0, <= 2021.3.13021>= 2022.1.0, < 2022.1.3106>= 2022.2.6729, < 2022.2.7718>= 2022.3.348, < 2022.3.7782

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Determine your Octopus Server version
    Check the version in the Octopus UI (Help -> About), or query the API endpoint GET /api, or inspect the installation logs. Compare the version number against the affected ranges: 3.0.0-4.1.10, 2018.1.0-2021.3.13021, 2022.1.0-2022.1.3105, 2022.2.6729-2022.2.7717, 2022.3.348-2022.3.7781.
    Affected if The installed version falls within any of these ranges.
  2. Identify if the built-in package feed is configured
    Navigate to Infrastructure -> Feeds in the Octopus UI and look for the built-in feed (typically named 'Octopus Server'). Alternatively, query the API endpoint GET /api/feeds and look for a feed with type 'BuiltIn'.
    Affected if The built-in package feed is present and active.
  3. Check for recent package re-indexing activity
    Review the Octopus Server logs for entries containing 're-index' or 'ReindexPackages' operations, or check the Task history for completed re-indexing tasks. This operation triggers the permission bypass vulnerability.
    Affected if A package re-indexing operation has been performed on the built-in feed.
  4. Verify current feed permissions
    Navigate to the built-in feed settings and review the associated user roles and permissions. Specifically check if users with limited or no upload permissions exist in the system.
    Affected if Users with restricted permissions exist and a re-index has occurred, as the vulnerability allows these users to upload packages after re-indexing.

You are affected if your Octopus Server version falls within the affected ranges AND the built-in package feed is in use AND a package re-indexing operation has been performed.

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.3106 / 2022.2.7718 / 2022.3.7782 or later
Fixed in 2022.1.31062022.2.77182022.3.7782
Interim mitigation

Upgrade Octopus Deploy to the patched version as specified in the vendor advisory. Review user role assignments and package feed permissions as part of remediation testing.

Recommended fix High confidence

2022.2.7718 or later (or latest 2022.2 LTS for older branches)

  1. Backup your Octopus Server database and configuration
  2. Identify which version branch you are currently on (2022.1.x, 2022.2.x, or older)
  3. For 2022.1.x branch: upgrade to version 2022.1.3106 or later
  4. For 2022.2.x branch: upgrade to version 2022.2.7718 or later
  5. For older branches (3.x, 4.x, 2018.x, 2021.x): upgrade to the latest 2022.2 LTS or later version
  6. After upgrade, verify that package upload permissions are correctly enforced in the built-in feed
Caveat Review release notes for your version branch for any breaking changes between your current and target version

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
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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