CVE-2022-1670
First published: Thu May 19 2022(Updated: )
When generating a user invitation code in Octopus Server, the validity of this code can be set for a specific number of users. It was possible to bypass this restriction of validity to create extra user accounts above the initial number of invited users.
Credit: security@octopus.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Octopus Deploy | >=0.9<2021.3.12533 | |
| Octopus Deploy | >=2022.1.0<2022.1.53 |
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-1670?
CVE-2022-1670 has been rated as a high severity vulnerability due to its potential for unauthorized user account creation.
How do I fix CVE-2022-1670?
To fix CVE-2022-1670, upgrade to a patched version of Octopus Server that is beyond the affected versions listed in the advisory.
What are the affected versions of Octopus Server for CVE-2022-1670?
CVE-2022-1670 affects Octopus Server versions prior to 2021.3.12533 and between 2022.1.0 and 2022.1.53.
What could happen if CVE-2022-1670 is exploited?
If exploited, CVE-2022-1670 could allow an attacker to create additional user accounts beyond the intended limit, potentially leading to unauthorized access.
Is there a workaround for CVE-2022-1670?
There is no known workaround for CVE-2022-1670, so updating to a secure version is the recommended mitigation.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/author
- agent/references
- agent/last-modified-date
- agent/event
- agent/description
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/octopus
- canonical/octopus deploy
- version/octopus deploy/0.9
- version/octopus deploy/2022.1.0