CVE-2022-2572
First published: Tue Nov 01 2022(Updated: )
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.
Credit: security@octopus.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Octopus Deploy | >=3.5<2022.1.3264 | |
| Octopus Deploy | >=2022.2.6729<2022.2.8277 | |
| Octopus Deploy | >=2022.3.348<2022.3.10586 | |
| Octopus Deploy | >=2022.4.791<2022.4.2898 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2022-2572?
CVE-2022-2572 is considered a medium-severity vulnerability as it allows API keys of disabled or deleted users to remain valid.
How do I fix CVE-2022-2572?
To fix CVE-2022-2572, update Octopus Server to a version that addresses this issue, specifically versions after 2022.4.791.
Which versions of Octopus Server are affected by CVE-2022-2572?
CVE-2022-2572 affects Octopus Server versions from 3.5 up to 2022.4.791.
What are the risks associated with CVE-2022-2572?
The risks of CVE-2022-2572 include unauthorized access if API keys of disabled or deleted users remain operational.
Who does CVE-2022-2572 impact?
CVE-2022-2572 impacts organizations using Octopus Server with external authentication providers that enable automated key management.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/weakness
- agent/severity
- agent/references
- agent/last-modified-date
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/octopus
- canonical/octopus deploy
- version/octopus deploy/3.5
- version/octopus deploy/2022.2.6729
- version/octopus deploy/2022.3.348
- version/octopus deploy/2022.4.791