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.
Metrics
Affected Vendors & Products
References
Link | Providers |
---|---|
https://github.com/OctopusDeploy/Issues/issues/4073 |
![]() ![]() |
History
No history.

Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-05T20:59:17.205Z
Reserved: 2017-12-13T00:00:00
Link: CVE-2017-17665

No data.

Status : Modified
Published: 2017-12-13T20:29:00.300
Modified: 2024-11-21T03:18:25.570
Link: CVE-2017-17665

No data.