Octopusdeploy
by Octopus
Source repositories
CVEs (63)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2022-2778 | Cri | 0.64 | 9.8 | 0.01 | Sep 30, 2022 | In affected versions of Octopus Deploy it is possible to bypass rate limiting on login using null bytes. | ||
| CVE-2018-11320 | Cri | 0.64 | 9.8 | 0.01 | May 21, 2018 | In Octopus Deploy 2018.4.4 through 2018.5.1, Octopus variables that are sourced from the target do not have sensitive values obfuscated in the deployment logs. | ||
| CVE-2018-18850 | Hig | 0.61 | 8.8 | 0.12 | Oct 31, 2018 | In Octopus Deploy 2018.8.0 through 2018.9.x before 2018.9.1, an authenticated user with permission to modify deployment processes could upload a maliciously crafted YAML configuration, potentially allowing for remote execution of arbitrary code, running in the same context as… | ||
| CVE-2026-0704 | Cri | 0.59 | 9.1 | 0.00 | Feb 25, 2026 | In affected version of Octopus Deploy it was possible to remove files and/or contents of files on the host using an API endpoint. The field lacked validation which could potentially result in ways to circumvent expected workflows. | ||
| CVE-2025-0539 | Hig | 0.57 | 8.8 | 0.00 | Apr 10, 2025 | In affected Microsoft Windows versions of Octopus Deploy, the server can be coerced into sending server-side requests that contain authentication material allowing a suitably positioned attacker to compromise the account running Octopus Server and potentially the host… | ||
| CVE-2024-2975 | Hig | 0.57 | 8.8 | 0.00 | Apr 9, 2024 | A race condition was identified through which privilege escalation was possible in certain configurations. | ||
| CVE-2022-4009 | Hig | 0.57 | 8.8 | 0.01 | Mar 16, 2023 | In affected versions of Octopus Deploy it is possible for a user to introduce code via offline package creation | ||
| CVE-2020-10678 | Hig | 0.57 | 8.8 | 0.01 | Mar 19, 2020 | In Octopus Deploy before 2020.1.5, for customers running on-premises Active Directory linked to their Octopus server, an authenticated user can leverage a bug to escalate privileges. | ||
| CVE-2018-5706 | Hig | 0.57 | 8.8 | 0.01 | Jan 16, 2018 | An issue was discovered in Octopus Deploy before 4.1.9. Any user with user editing permissions can modify teams to give themselves Administer System permissions even if they didn't have them, as demonstrated by use of the RoleEdit or TeamEdit permission. | ||
| CVE-2018-4862 | Hig | 0.57 | 8.8 | 0.01 | Jan 3, 2018 | In Octopus Deploy versions 3.2.11 - 4.1.5 (fixed in 4.1.6), an authenticated user with ProcessEdit permission could reference an Azure account in such a way as to bypass the scoping restrictions, resulting in a potential escalation of privileges. | ||
| CVE-2017-17665 | Hig | 0.57 | 8.8 | 0.01 | Dec 13, 2017 | In Octopus Deploy before 4.1.3, the machine update process doesn't check that the user has access to all environments. This allows an access-control bypass because the set of environments to which a machine is scoped may include environments in which the user lacks access. | ||
| CVE-2019-11632 | Hig | 0.53 | 8.1 | 0.01 | May 1, 2019 | In Octopus Deploy 2019.1.0 through 2019.3.1 and 2019.4.0 through 2019.4.5, an authenticated user with the VariableViewUnscoped or VariableEditUnscoped permission scoped to a specific project could view or edit unscoped variables from a different project. (These permissions are… | ||
| CVE-2021-26556 | Hig | 0.51 | 7.8 | 0.00 | Oct 7, 2021 | When Octopus Server is installed using a custom folder location, folder ACLs are not set correctly and could lead to an unprivileged user using DLL side-loading to gain privileged access. | ||
| CVE-2022-2883 | Hig | 0.49 | 7.5 | 0.01 | Feb 22, 2023 | In affected versions of Octopus Deploy it is possible to upload a zipbomb file as a task which results in Denial of Service | ||
| CVE-2022-3460 | Hig | 0.49 | 7.5 | 0.01 | Jan 3, 2023 | In affected versions of Octopus Deploy it is possible for certain types of sensitive variables to inadvertently become unmasked when viewed in variable preview. | ||
| CVE-2022-2075 | Hig | 0.49 | 7.5 | 0.01 | Aug 19, 2022 | In affected versions of Octopus Deploy it is possible to perform a Regex Denial of Service targeting the build information request validation. | ||
| CVE-2022-2074 | Hig | 0.49 | 7.5 | 0.01 | Aug 19, 2022 | In affected versions of Octopus Deploy it is possible to perform a Regex Denial of Service using the Variable Project Template. | ||
| CVE-2022-2049 | Hig | 0.49 | 7.5 | 0.01 | Aug 19, 2022 | In affected versions of Octopus Deploy it is possible to perform a Regex Denial of Service via the package upload function. | ||
| CVE-2022-2013 | Hig | 0.49 | 7.5 | 0.01 | Jun 13, 2022 | In Octopus Server after version 2022.1.1495 and before 2022.1.2647 if private spaces were enabled via the experimental feature flag all new users would have access to the Script Console within their private space. | ||
| CVE-2021-30183 | Hig | 0.49 | 7.5 | 0.01 | May 14, 2021 | Cleartext storage of sensitive information in multiple versions of Octopus Server where in certain situations when running import or export processes, the password used to encrypt and decrypt sensitive values would be written to the logs in plaintext. |
- risk 0.64cvss 9.8epss 0.01
In affected versions of Octopus Deploy it is possible to bypass rate limiting on login using null bytes.
- risk 0.64cvss 9.8epss 0.01
In Octopus Deploy 2018.4.4 through 2018.5.1, Octopus variables that are sourced from the target do not have sensitive values obfuscated in the deployment logs.
- risk 0.61cvss 8.8epss 0.12
In Octopus Deploy 2018.8.0 through 2018.9.x before 2018.9.1, an authenticated user with permission to modify deployment processes could upload a maliciously crafted YAML configuration, potentially allowing for remote execution of arbitrary code, running in the same context as…
- risk 0.59cvss 9.1epss 0.00
In affected version of Octopus Deploy it was possible to remove files and/or contents of files on the host using an API endpoint. The field lacked validation which could potentially result in ways to circumvent expected workflows.
- risk 0.57cvss 8.8epss 0.00
In affected Microsoft Windows versions of Octopus Deploy, the server can be coerced into sending server-side requests that contain authentication material allowing a suitably positioned attacker to compromise the account running Octopus Server and potentially the host…
- risk 0.57cvss 8.8epss 0.00
A race condition was identified through which privilege escalation was possible in certain configurations.
- risk 0.57cvss 8.8epss 0.01
In affected versions of Octopus Deploy it is possible for a user to introduce code via offline package creation
- risk 0.57cvss 8.8epss 0.01
In Octopus Deploy before 2020.1.5, for customers running on-premises Active Directory linked to their Octopus server, an authenticated user can leverage a bug to escalate privileges.
- risk 0.57cvss 8.8epss 0.01
An issue was discovered in Octopus Deploy before 4.1.9. Any user with user editing permissions can modify teams to give themselves Administer System permissions even if they didn't have them, as demonstrated by use of the RoleEdit or TeamEdit permission.
- risk 0.57cvss 8.8epss 0.01
In Octopus Deploy versions 3.2.11 - 4.1.5 (fixed in 4.1.6), an authenticated user with ProcessEdit permission could reference an Azure account in such a way as to bypass the scoping restrictions, resulting in a potential escalation of privileges.
- risk 0.57cvss 8.8epss 0.01
In Octopus Deploy before 4.1.3, the machine update process doesn't check that the user has access to all environments. This allows an access-control bypass because the set of environments to which a machine is scoped may include environments in which the user lacks access.
- risk 0.53cvss 8.1epss 0.01
In Octopus Deploy 2019.1.0 through 2019.3.1 and 2019.4.0 through 2019.4.5, an authenticated user with the VariableViewUnscoped or VariableEditUnscoped permission scoped to a specific project could view or edit unscoped variables from a different project. (These permissions are…
- risk 0.51cvss 7.8epss 0.00
When Octopus Server is installed using a custom folder location, folder ACLs are not set correctly and could lead to an unprivileged user using DLL side-loading to gain privileged access.
- risk 0.49cvss 7.5epss 0.01
In affected versions of Octopus Deploy it is possible to upload a zipbomb file as a task which results in Denial of Service
- risk 0.49cvss 7.5epss 0.01
In affected versions of Octopus Deploy it is possible for certain types of sensitive variables to inadvertently become unmasked when viewed in variable preview.
- risk 0.49cvss 7.5epss 0.01
In affected versions of Octopus Deploy it is possible to perform a Regex Denial of Service targeting the build information request validation.
- risk 0.49cvss 7.5epss 0.01
In affected versions of Octopus Deploy it is possible to perform a Regex Denial of Service using the Variable Project Template.
- risk 0.49cvss 7.5epss 0.01
In affected versions of Octopus Deploy it is possible to perform a Regex Denial of Service via the package upload function.
- risk 0.49cvss 7.5epss 0.01
In Octopus Server after version 2022.1.1495 and before 2022.1.2647 if private spaces were enabled via the experimental feature flag all new users would have access to the Script Console within their private space.
- risk 0.49cvss 7.5epss 0.01
Cleartext storage of sensitive information in multiple versions of Octopus Server where in certain situations when running import or export processes, the password used to encrypt and decrypt sensitive values would be written to the logs in plaintext.
Page 1 of 4