dbcve.org
Octopus ServerApplication · Octopus

CVE-2025-0589

MEDIUM · 5.3 CVSS v3.1 Published 2025-02-11
Fix available
A fix is available. Upgrade to 2024.3.13071 / 2024.4.7065 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 Deploy where customers are using Active Directory for authentication it was possible for an unauthenticated user to make an API request against two endpoints which would retrieve some data from the associated Active Directory. The requests when crafted correctly would return specific information from user profiles (Email address/UPN and Display name) from one endpoint and group information ( Group ID and Display name) from the other. This vulnerability does not expose data within the Octopus Server product itself.

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 versions using Active Directory authentication contain two API endpoints accessible to unauthenticated users that return sensitive AD user profile information (email/UPN, display name) and group information (group ID, display name). This information disclosure does not expose Octopus Server internal data but exposes organizational directory metadata to anonymous attackers.

MitigationApply vendor-supplied patch or hotfix for CVE-2025-0589. If unavailable, temporarily disable AD authentication or implement network-level access controls to restrict these API endpoints until a fix is 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:>= 2020.3.3, < 2024.3.13071>= 2024.4.401, < 2024.4.7065

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 Octopus Server installation and version
    Locate the Octopus Server instance and determine its installed version number (typically visible in the UI under About or in the server logs)
    Affected if The installed version falls within >= 2020.3.3, < 2024.3.13071 OR >= 2024.4.401, < 2024.4.7065
  2. Verify Active Directory authentication is enabled
    Check the Octopus Server authentication configuration to confirm Active Directory (or Azure AD/Integrated Windows Authentication) is configured as an authentication provider
    Affected if Active Directory authentication is enabled and configured on the Octopus Server
  3. Test unauthenticated access to user profile API endpoint
    Send an HTTP request to the suspected user info API endpoint without providing authentication credentials (common paths include /api/users/me or similar AD-related endpoints)
    Affected if The endpoint returns AD user profile information such as email, UPN, or display name without requiring authentication
  4. Test unauthenticated access to group information API endpoint
    Send an HTTP request to the suspected group API endpoint without providing authentication credentials
    Affected if The endpoint returns AD group information such as group IDs or display names without requiring authentication

The environment is affected if Octopus Server version is in the vulnerable range, Active Directory authentication is configured, and either API endpoint returns sensitive AD information to unauthenticated requests.

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 2024.3.13071 / 2024.4.7065 or later
Fixed in 2024.3.130712024.4.7065
Interim mitigation

Apply vendor-supplied patch or hotfix for CVE-2025-0589. If unavailable, temporarily disable AD authentication or implement network-level access controls to restrict these API endpoints until a fix is available.

Recommended fix High confidence

2024.3.13071 or later (2024.3.x LTS); 2024.4.7065 or later (2024.4.x)

  1. 1. Identify the current Octopus Server version by navigating to the Configuration > Nodes page in the Octopus Web Portal
  2. 2. If running a version >= 2020.3.3 and < 2024.3.13071, plan an upgrade to version 2024.3.13071 or later in the 2024.3.x LTS release line
  3. 3. If running a version >= 2024.4.401 and < 2024.4.7065, plan an upgrade to version 2024.4.7065 or later in the 2024.4.x release line
  4. 4. Before upgrading, review the Octopus Deploy release notes for the target version to understand any required migration steps
  5. 5. Perform a full backup of the Octopus database and configuration following standard backup procedures
  6. 6. Execute the upgrade following Octopus Deploy upgrade documentation
  7. 7. After upgrade, verify the Active Directory authentication is functioning correctly by testing user logins

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,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 $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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