Octopus Server: Improper Authentication
CVE-2022-2572 is a critical-severity improper authentication vulnerability in Octopus Server from Octopus Deploy, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 2022.1.3264, 2022.2.8277, 2022.3.10586 as the first without the flaw, so updating Octopus Server to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1% chance of exploitation within 30 days, higher than 64% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Octopus Server to 2022.1.3264 or 2022.2.8277 or 2022.3.10586 or 2022.4.2898, whichever matches your release line, or a later version.
- Read the advisory on advisories.octopus.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Octopus Deploy | Octopus Server | 3.5; before 2022.1.3264; 2022.2.6729; before 2022.2.8277; 2022.3.348; before 2022.3.10586; 2022.4.791; before 2022.4.2898 | 2022.1.3264, 2022.2.8277, 2022.3.10586, 2022.4.2898 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.8 | Critical | NVD |
| CVSS 3.1 | 9.8 | Critical | CISA (ADP) |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Authentication
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
How developers prevent this class of flaw
- Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Octopus Server
- 8.7 High severity
- 8.7 High severity
- 8.7 High severity
- 7.1 High severity
- 7.7 High severity
- 8.7 High severity
Recent Improper Authentication vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 7.5 High severity
Spotted an error? Tell us.