Security readout for executives and security teams
Plain-English summary
Octopus Server could keep API keys working after a user was disabled or deleted in an external authentication provider. That means removing a person’s identity access might not remove their API access, creating a serious risk of unauthorized control over deployments and secrets.
Executive priority
Prioritize this for any Octopus Server environment tied to deployment automation, production releases, or secrets. The business risk is unauthorized deployment control after offboarding or account disablement.
Technical view
CVE-2022-2572 is an authentication revocation failure in Octopus Server deployments using external authentication. API keys for disabled or deleted users could remain valid after access was revoked. The record maps this to CWE-287 and assigns CVSS 3.1 score 9.8 with network, low-complexity, no-privilege, no-user-interaction characteristics.
Likely exposure
Exposure is most likely where Octopus Server uses an external authentication provider and runs an affected version listed in the CVE bundle, including 3.5, 2022.2.6729, 2022.3.348, or 2022.4.791. The provided evidence does not define exact fixed versions.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The risk is still high because stale API keys may retain privileged deployment access after an organization believes user access has been removed.
Researcher notes
Evidence is limited to the CVE metadata and Octopus advisory reference. Do not assume exploit availability, affected CPEs, or fixed versions beyond the supplied sources. Focus validation on identity revocation, API key lifecycle, and post-revocation activity.
Mitigation direction
- Review Octopus advisory SA2022-23 and follow vendor guidance.
- Inventory Octopus Server versions and external authentication usage.
- Apply vendor-recommended update or mitigation once confirmed.
- Audit API keys for disabled or deleted users.
- Rotate suspect API keys through approved administrative procedures.
Validation and detection
- Compare Octopus Server versions against affected versions in the CVE bundle.
- Confirm whether access is managed by an external authentication provider.
- Review disabled and deleted users for remaining API keys.
- Check audit logs for API key use after user revocation.
- Document any compensating controls and unresolved vendor guidance gaps.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-287: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-2572 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://advisories.octopus.com/post/2022/sa2022-23/CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Authentication
Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.