dbcve.org
Octopus ServerApplication · Octopus

CVE-2024-2975

HIGH · 7.5 CVSS v3.1 Developing Published 2024-04-09
Fix available
A fix is available. Upgrade to 2023.4.8432 / 2024.1.12087 or later.
See remediation →
81/100
Remediation priority · High
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
A race condition was identified through which privilege escalation was possible in certain configurations.

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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-01.

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, < 2023.4.8432>= 2024.1.437, < 2024.1.12087>= 2024.2.101, < 2024.2.2075

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

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

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 2023.4.8432 / 2024.1.12087 / 2024.2.2075 or later
Fixed in 2023.4.84322024.1.120872024.2.2075
Recommended fix High confidence

2024.2.2075 (or latest 2024.2.x LTS), 2024.1.12087 (or latest 2024.1.x), or 2023.4.8432 (or latest 2023.4.x LTS - note 2023.4 is older branch)

  1. 1. Identify your current Octopus Server version from the System node in the web interface or via `octo version` CLI command
  2. 2. Based on your current version branch, plan upgrade to: 2023.4.8432 or later (if on 2023.4.x), 2024.1.12087 or later (if on 2024.1.x), or 2024.2.2075 or later (if on 2024.2.x)
  3. 3. Review Octopus Server upgrade prerequisites and backup procedures at https://octopus.com/docs/administration/upgrading
  4. 4. Perform a full database backup before upgrading
  5. 5. Download the appropriate installer for your target version from https://octopus.com/downloads
  6. 6. Run the installer on the Octopus Server node, following the upgrade wizard
  7. 7. After upgrade, verify the Octopus Server is running the patched version via the System node
Caveat Review upgrade notes for your version path - upgrading across major version branches may have breaking changes; 2023.4 is an older LTS branch so consider upgrading to 2024.x if possible

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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