CVE-2022-2572
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 affected versions of Octopus Server where access is managed by an external authentication provider, it was possible that the API key/keys of a disabled/deleted user were still valid after the access was revoked.
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 confidenceIn affected Octopus Server versions using external authentication providers (e.g., Active Directory, Azure AD, Okta), when a user's access is disabled or their account is deleted, their API keys remain valid and continue to function, allowing continued system access even after access revocation.
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.5, < 2022.1.3264>= 2022.2.6729, < 2022.2.8277>= 2022.3.348, < 2022.3.10586>= 2022.4.791, < 2022.4.2898CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Octopus Server versionNavigate to the Octopus Web Portal, go to Configuration > About, or run 'octopus.server --version' from the server hostAffected if Installed version falls within any of these ranges: >= 3.5 and < 2022.1.3264, OR >= 2022.2.6729 and < 2022.2.8277, OR >= 2022.3.348 and < 2022.3.10586, OR >= 2022.4.791 and < 2022.4.2898
-
Verify external authentication is configuredGo to Configuration > Authentication Providers in the Octopus Web Portal and confirm an external provider (Active Directory, Azure AD, Okta, or other) is enabledAffected if External authentication provider is enabled
-
List all API keys in the systemGo to Configuration > API Keys in the Octopus Web Portal to view all active API keys and their associated usersAffected if API keys exist in the system
-
Identify users disabled or deleted in external directoryCross-reference Octopus user accounts with the external directory (AD/Azure AD/Okta). Check the Octopus user list at Configuration > Users and compare account status with the external identity providerAffected if Any Octopus user accounts correspond to external identities that have been disabled or deleted in the external provider but still appear active in Octopus
-
Verify API keys for disabled/deleted users still functionFor any identified disabled/deleted external users, attempt to use their API key against the Octopus API endpoint (e.g., GET /api/users/{userId}) to confirm the key remains validAffected if API keys for disabled or deleted external users are accepted and return valid responses
If the Octopus Server version is within an affected range AND external authentication is configured AND any API keys remain functional for users whose external accounts have been disabled or deleted, the environment is vulnerable to CVE-2022-2572.
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.
dbcve · scoped2022.1.32642022.2.82772022.3.10586
Manually review and revoke all API keys associated with disabled or deleted users; implement a process to ensure API keys are automatically invalidated when users are deprovisioned through the external identity provider.
2022.4.2898 (or latest 2022.4 LTS)
- 1. Identify the currently installed Octopus Server version by checking the UI or using `octopus.server --version`
- 2. Determine which version range your current installation falls into (2022.1.x, 2022.2.x, 2022.3.x, or 2022.4.x)
- 3. Download the appropriate fixed version from octopus.com/downloads: 2022.1.3264 or later for 2022.1 line, 2022.2.8277 or later for 2022.2 line, 2022.3.10586 or later for 2022.3 line, or 2022.4.2898 or later for 2022.4 line
- 4. Review the Octopus Server upgrade guide at docs.octopus.com for your migration path
- 5. Back up your Octopus database and configuration before upgrading
- 6. Install the fixed version following standard upgrade procedures
- 7. After upgrade, verify that API keys for disabled/deleted users are properly invalidated by testing with previously used keys
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2572 — 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-2022-2572 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