dbcve.org
Octopus DeployApplication · Octopus

CVE-2020-10678

HIGH · 8.8 CVSS v3.1 Published 2020-03-19
Fix available
A fix is available. Upgrade to 2020.1.5 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 Octopus Deploy before 2020.1.5, for customers running on-premises Active Directory linked to their Octopus server, an authenticated user can leverage a bug to escalate privileges.

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 before version 2020.1.5 contains a privilege escalation vulnerability in on-premises Active Directory integrated deployments. An authenticated AD user can exploit a bug to gain elevated privileges beyond what their AD group membership should allow.

MitigationUpgrade Octopus Deploy to version 2020.1.5 or later. Review user role assignments and audit AD group mappings after patching.

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 DeployApplication
Affected:< 2020.1.5

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. Determine Octopus Deploy version
    Log into the Octopus Web UI as an administrator, then navigate to the Configuration > Nodes page, or use the API endpoint /api/serverstatus to retrieve the server version.
    Affected if The displayed version is earlier than 2020.1.5 (for example, 2020.1.4, 2020.1.0, or any version with a major.minor.patch number lower than 2020.1.5).
  2. Verify Active Directory integration is enabled
    In the Octopus Web UI, go to Configuration > Authentication > Active Directory, or check the /api/configuration/authentication-providers endpoint via the API.
    Affected if Active Directory authentication is configured and enabled for the Octopus instance.
  3. Confirm on-premises Octopus deployment
    Determine whether this is a self-hosted (on-premises) Octopus Deploy installation rather than Octopus Cloud.
    Affected if The Octopus Server is hosted on infrastructure you manage (not the hosted Octopus Cloud service).

If the installed Octopus Deploy version is before 2020.1.5, Active Directory integration is enabled, and this is an on-premises deployment, the environment is affected by this privilege escalation vulnerability.

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.

From vendor data
Upgrade available Upgrade to 2020.1.5 or later
Fixed in 2020.1.5
Interim mitigation

Upgrade Octopus Deploy to version 2020.1.5 or later. Review user role assignments and audit AD group mappings after patching.

Fix this in Octopus Deploy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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