Description
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.
Analysis and contextual insights are available on OpenCVE Cloud.
Remediation
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2017-8823 | 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. |
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.000Z
Link: CVE-2017-17665
No data.
Status : Modified
Published: 2017-12-13T20:29:00.300
Modified: 2026-05-13T00:24:29.033
Link: CVE-2017-17665
No data.
OpenCVE Enrichment
No data.
Weaknesses
EUVD