In affected versions of Octopus Server where access is managed by an external authentication provider, it was possibl…
Octopus Deploy Octopus Server
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Octopus Deploy Octopus Server |
| No fix yet |
Octopus Deploy Octopus Server
| Product | Affected | Fixed in |
|---|---|---|
| Octopus Deploy Octopus Server |
| No fix yet |
In 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.
From the CVE record · Octopus
In affected Octopus Server installations using an external authentication provider, API keys belonging to a disabled or deleted user could remain valid after access was revoked. Someone with one of those keys could continue to use it despite the user's revoked access; the input does not specify whether this requires network or local access or user interaction.
Teams running Octopus Deploy Octopus Server with an external authentication provider should check whether their version is affected.