Note:
This project will be discontinued after December 13, 2021. [more]
Product:
Octopus_deploy
(Octopus)Repositories |
Unknown: This might be proprietary software. |
#Vulnerabilities | 31 |
Date | Id | Summary | Products | Score | Patch | Annotated |
---|---|---|---|---|---|---|
2020-03-19 | CVE-2020-10678 | 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. | Octopus_deploy | 8.8 | ||
2020-04-28 | CVE-2020-12286 | 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. | Octopus_deploy | 4.3 | ||
2020-06-19 | CVE-2020-14470 | 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. | Octopus_deploy | 6.5 | ||
2020-10-22 | CVE-2020-27155 | 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. | Octopus_deploy | 7.5 | ||
2020-10-12 | CVE-2020-25825 | In Octopus Deploy 3.1.0 to 2020.4.0, certain scripts can reveal sensitive information to the user in the task logs. | Octopus_deploy | 7.5 | ||
2020-09-09 | CVE-2020-24566 | 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. | Octopus_deploy | N/A | ||
2019-11-28 | CVE-2019-19375 | 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.) | Octopus_deploy | N/A | ||
2019-11-18 | CVE-2019-19084 | 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. | Octopus_deploy | N/A | ||
2017-12-13 | CVE-2017-17665 | 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. | Octopus_deploy | 8.8 | ||
2017-10-19 | CVE-2017-15611 | In Octopus before 3.17.7, an authenticated user who was explicitly granted the permission to invite new users (aka UserInvite) can invite users to teams with escalated privileges. | Octopus_deploy | 6.5 |