CVE-2017-17665
First published: Wed Dec 13 2017(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Octopus Octopus Deploy | <4.1.3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-17665?
The severity of CVE-2017-17665 is rated as high with a score of 8.8.
How do I fix CVE-2017-17665?
To fix CVE-2017-17665, upgrade Octopus Deploy to version 4.1.3 or later.
What does CVE-2017-17665 allow an attacker to do?
CVE-2017-17665 allows an attacker to bypass access controls by updating machines in environments where they lack permissions.
Which versions of Octopus Deploy are affected by CVE-2017-17665?
CVE-2017-17665 affects all versions of Octopus Deploy prior to 4.1.3.
What type of vulnerability is CVE-2017-17665 classified as?
CVE-2017-17665 is classified as an access-control bypass vulnerability.
- collector/nvd-index
- vendor/octopus
- product/octopus deploy
- canonical/octopus octopus deploy