In affected versions of Octopus Deploy it is possible to unmask variable secrets using the variable preview function
Source: Octopus Deploy
Max CVSS
5.3
EPSS Score
0.05%
Published
2023-05-02
Updated
2023-12-14
In affected Octopus Server versions when the server HTTP and HTTPS bindings are configured to localhost, Octopus Server will allow open redirects.
Source: Octopus Deploy
Max CVSS
6.1
EPSS Score
0.07%
Published
2022-02-07
Updated
2022-07-27
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.
Source: Octopus Deploy
Max CVSS
7.5
EPSS Score
0.15%
Published
2022-06-13
Updated
2022-06-17
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.
Source: Octopus Deploy
Max CVSS
7.8
EPSS Score
0.06%
Published
2021-10-07
Updated
2022-07-27
An issue was discovered in Octopus Deploy through 2020.4.4. If enabled, the websocket endpoint may allow an untrusted tentacle host to present itself as a trusted one.
Source: MITRE
Max CVSS
7.5
EPSS Score
0.11%
Published
2020-10-22
Updated
2020-10-30
In Octopus Deploy through 2020.4.2, an attacker could redirect users to an external site via a modified HTTP Host header.
Source: MITRE
Max CVSS
6.1
EPSS Score
0.08%
Published
2020-10-26
Updated
2022-06-03
In Octopus Deploy 3.1.0 to 2020.4.0, certain scripts can reveal sensitive information to the user in the task logs.
Source: MITRE
Max CVSS
7.5
EPSS Score
0.12%
Published
2020-10-12
Updated
2020-10-26
In Octopus Deploy 2020.3.x before 2020.3.4 and 2020.4.x before 2020.4.1, if an authenticated user creates a deployment or runbook process using Azure steps and sets the step's execution location to run on the server/worker, then (under certain circumstances) the account password is exposed in cleartext in the verbose task logs output.
Source: MITRE
Max CVSS
7.5
EPSS Score
0.29%
Published
2020-09-09
Updated
2020-09-10
In Octopus Deploy 2018.8.0 through 2019.x before 2019.12.2, an authenticated user with could trigger a deployment that leaks the Helm Chart repository password.
Source: MITRE
Max CVSS
6.5
EPSS Score
0.07%
Published
2020-06-19
Updated
2021-07-21
In Octopus Deploy before 2019.12.9 and 2020 before 2020.1.12, the TaskView permission is not scoped to any dimension. For example, a scoped user who is scoped to only one tenant can view server tasks scoped to any other tenant.
Source: MITRE
Max CVSS
4.3
EPSS Score
0.06%
Published
2020-04-28
Updated
2021-07-21
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.
Source: MITRE
Max CVSS
8.8
EPSS Score
0.10%
Published
2020-03-19
Updated
2021-07-21
In Octopus Deploy before 2019.10.6, an authenticated user with TeamEdit permission could send a malformed Team API request that bypasses input validation and causes an application level denial of service condition. (The fix for this was also backported to LTS 2019.9.8 and LTS 2019.6.14.)
Source: MITRE
Max CVSS
6.5
EPSS Score
0.08%
Published
2019-11-28
Updated
2021-07-21
In Octopus Deploy before 2019.10.7, in a configuration where SSL offloading is enabled, the CSRF cookie was sometimes sent without the secure attribute. (The fix for this was backported to LTS versions 2019.6.14 and 2019.9.8.)
Source: MITRE
Max CVSS
5.3
EPSS Score
0.06%
Published
2019-11-28
Updated
2020-08-24
In Octopus Deploy 3.3.0 through 2019.10.4, an authenticated user with PackagePush permission to upload packages could upload a maliciously crafted package, triggering an exception that exposes underlying operating system details.
Source: MITRE
Max CVSS
4.3
EPSS Score
0.05%
Published
2019-11-18
Updated
2019-11-20
In Octopus Deploy 2019.4.0 through 2019.6.x before 2019.6.6, and 2019.7.x before 2019.7.6, an authenticated system administrator is able to view sensitive values by visiting a server configuration page or making an API call.
Source: MITRE
Max CVSS
4.9
EPSS Score
0.11%
Published
2019-08-05
Updated
2022-07-27
In Octopus Deploy versions 3.0.19 to 2019.7.2, when a web request proxy is configured, an authenticated user (in certain limited circumstances) could trigger a deployment that writes the web request proxy password to the deployment log in cleartext. This is fixed in 2019.7.3. The fix was back-ported to LTS 2019.6.5 as well as LTS 2019.3.7.
Source: MITRE
Max CVSS
6.5
EPSS Score
0.07%
Published
2019-07-25
Updated
2019-08-02
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 only used in custom User Roles and do not affect built in User Roles.)
Source: MITRE
Max CVSS
8.1
EPSS Score
0.07%
Published
2019-05-01
Updated
2022-07-27
An Information Exposure issue in the Terraform deployment step in Octopus Deploy before 2019.1.8 (and before 2018.10.4 LTS) allows remote authenticated users to view sensitive Terraform output variables via log files.
Source: MITRE
Max CVSS
6.5
EPSS Score
0.10%
Published
2019-02-20
Updated
2022-07-27
In Octopus Deploy 3.0 onwards (before 2018.6.7), an authenticated user with incorrect permissions may be able to create Accounts under the Infrastructure menu.
Source: MITRE
Max CVSS
6.5
EPSS Score
0.05%
Published
2018-06-26
Updated
2019-10-03
In Octopus Deploy 3.4.x before 2018.4.7, an authenticated user is able to view/update/save variable values within the Tenant Variables area for Environments that do not exist within their associated Team scoping. This occurs in situations where this authenticated user also belongs to multiple teams, where one of the Teams has the VariableEdit permission or VariableView permissions for the Environment.
Source: MITRE
Max CVSS
5.5
EPSS Score
0.06%
Published
2018-05-01
Updated
2018-06-13
In Octopus Deploy before 2018.4.7, target and tenant tag variable scopes were not checked against the list of tenants the user has access to.
Source: MITRE
Max CVSS
7.5
EPSS Score
0.17%
Published
2018-04-30
Updated
2019-10-03
In Octopus Deploy 2.0 and later before 2018.3.7, an authenticated user, with variable edit permissions, can scope some variables to targets greater than their permissions should allow. In other words, they can see machines beyond their team's scoped environments.
Source: MITRE
Max CVSS
6.5
EPSS Score
0.07%
Published
2018-03-27
Updated
2020-08-24
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.
Source: MITRE
Max CVSS
8.8
EPSS Score
0.09%
Published
2018-01-16
Updated
2019-10-03
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.
Source: MITRE
Max CVSS
8.8
EPSS Score
0.09%
Published
2018-01-03
Updated
2019-10-03
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.
Source: MITRE
Max CVSS
8.8
EPSS Score
0.10%
Published
2017-12-13
Updated
2019-10-03
31 vulnerabilities found
1 2
This web site uses cookies for managing your session, storing preferences, website analytics and additional purposes described in our privacy policy.
By using this web site you are agreeing to CVEdetails.com terms of use!