Octopus Server: Authentication Bypass by Capture-replay
CVE-2022-2780 is a high-severity authentication bypass by capture-replay vulnerability in Octopus Server from Octopus Deploy, with a CVSS 3.1 base score of 8.1 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.3180, 2022.2.7965, 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 0.63% chance of exploitation within 30 days, higher than 51% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Octopus Server to 2022.1.3180 or 2022.2.7965 or 2022.3.10586, 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 | 2021.2.994; before 2022.1.3180; 2022.2.6729; before 2022.2.7965; 2022.3.348; before 2022.3.10586 | 2022.1.3180, 2022.2.7965, 2022.3.10586 |
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
- HighSuccess depends on conditions outside the attacker's control.
- 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:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.1 | High | NVD |
| CVSS 3.1 | 8.1 | High | CISA (ADP) |
Official description
In affected versions of Octopus Server it is possible to use the Git Connectivity test function on the VCS project to initiate an SMB request resulting in the potential for an NTLM relay attack.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Authentication Bypass by Capture-replay
A capture-replay flaw exists when the design of the product makes it possible for a malicious user to sniff network traffic and bypass authentication by replaying it to the server in question to the same effect as the original message (or with minor changes).
How developers prevent this class of flaw
- Utilize some sequence or time stamping functionality along with a checksum which takes this into account in order to ensure that messages can be parsed only once.
- Since any attacker who can listen to traffic can see sequence numbers, it is necessary to sign messages with some kind of cryptography to ensure that sequence numbers are not simply doctored along with content.
More Authentication Bypass by Capture-replay vulnerabilities (CWE-294)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, 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 Authentication Bypass by Capture-replay vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.