Octopus: >> Octopus Deploy >> 3.17.12 Security Vulnerabilities
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.
CVSS Score
7.5
EPSS Score
0.002
Published
2018-04-30
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.
CVSS Score
6.5
EPSS Score
0.003
Published
2018-03-27
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.
CVSS Score
8.8
EPSS Score
0.002
Published
2018-01-16
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.
CVSS Score
8.8
EPSS Score
0.002
Published
2018-01-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.
CVSS Score
8.8
EPSS Score
0.003
Published
2017-12-13
Page 2