CVE-2018-12884
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 · uneditedIn Octopus Deploy 3.0 onwards (before 2018.6.7), an authenticated user with incorrect permissions may be able to create Accounts under the Infrastructure menu.
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 · high confidenceOctopus Deploy versions 3.0 through 2018.6.6 contain a broken access control vulnerability where authenticated users with insufficient permissions can still create Accounts via the Infrastructure menu. The application fails to properly enforce authorization checks before allowing account creation.
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= 3.0CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Octopus Deploy versionAccess the Octopus Deploy web UI and navigate to the system health or about page, or check the installation directory for version information. Common locations include the UI footer, /about page, or the installation manifest file.Affected if The installed version falls within the range 3.0 to 2018.6.6 inclusive.
-
Verify user role configurationLog into Octopus Deploy as an administrator and navigate to the Users or Teams configuration section to review defined roles and their permission levels.Affected if Roles other than Administrator or built-in high-privilege roles exist with limited permissions.
-
Test Infrastructure menu access for low-privilege usersCreate or use a test user account assigned to a limited role (non-Administrator), then attempt to access the Infrastructure menu and navigate to the Accounts section.Affected if The limited user can access the Infrastructure menu and view the account creation interface without receiving an authorization error.
-
Confirm account creation permission bypassUsing the limited-privilege test user from the previous check, attempt to create a new Account (such as an Azure account or AWS account) via the Infrastructure menu.Affected if The account creation succeeds or the interface allows submission without triggering a permission denial message.
A user is affected if they run Octopus Deploy versions 3.0 through 2018.6.6 and have non-administrator accounts that can access the Infrastructure menu and create accounts despite lacking proper authorization.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Octopus Deploy to version 2018.6.7 or later, which contains the fix for this permission bypass vulnerability.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2018-12884 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-12884 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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