Filtered by vendor Octopus
Subscriptions
Total
83 CVE
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2020-26161 | 1 Octopus | 1 Octopus Deploy | 2022-06-03 | 6.1 Medium |
| In Octopus Deploy through 2020.4.2, an attacker could redirect users to an external site via a modified HTTP Host header. | ||||
| CVE-2021-31821 | 2 Microsoft, Octopus | 2 Windows, Tentacle | 2022-01-26 | 5.5 Medium |
| When the Windows Tentacle docker image starts up it logs all the commands that it runs along with the arguments, which writes the Octopus Server API key in plaintext. This does not affect the Linux Docker image | ||||
| CVE-2019-19376 | 1 Octopus | 1 Octopus Deploy | 2021-07-21 | 6.5 Medium |
| In Octopus Deploy before 2019.10.6, an authenticated user with TeamEdit permission could send a malformed Team API request that bypasses input validation and causes an application level denial of service condition. (The fix for this was also backported to LTS 2019.9.8 and LTS 2019.6.14.) | ||||
| CVE-2020-10678 | 1 Octopus | 1 Octopus Deploy | 2021-07-21 | 8.8 High |
| 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. | ||||
| CVE-2020-12286 | 1 Octopus | 1 Octopus Deploy | 2021-07-21 | 4.3 Medium |
| 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. | ||||
| CVE-2020-14470 | 1 Octopus | 1 Octopus Deploy | 2021-07-21 | 6.5 Medium |
| 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. | ||||
| CVE-2021-21270 | 1 Octopus | 1 Octopusdsc | 2021-02-01 | 5.5 Medium |
| OctopusDSC is a PowerShell module with DSC resources that can be used to install and configure an Octopus Deploy Server and Tentacle agent. In OctopusDSC version 4.0.977 and earlier a customer API key used to connect to Octopus Server is exposed via logging in plaintext. This vulnerability is patched in version 4.0.1002. | ||||
| CVE-2020-27155 | 1 Octopus | 1 Octopus Deploy | 2020-10-30 | 7.5 High |
| 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. | ||||
| CVE-2020-25825 | 1 Octopus | 1 Octopus Deploy | 2020-10-26 | 7.5 High |
| In Octopus Deploy 3.1.0 to 2020.4.0, certain scripts can reveal sensitive information to the user in the task logs. | ||||
| CVE-2020-24566 | 1 Octopus | 1 Octopus Deploy | 2020-09-10 | 7.5 High |
| 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. | ||||
| CVE-2019-19375 | 1 Octopus | 1 Octopus Deploy | 2020-08-24 | 5.3 Medium |
| 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.) | ||||
| CVE-2018-9039 | 1 Octopus | 1 Octopus Deploy | 2020-08-24 | N/A |
| 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. | ||||
| CVE-2019-19084 | 1 Octopus | 1 Octopus Deploy | 2019-11-20 | 4.3 Medium |
| 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. | ||||
| CVE-2017-15609 | 1 Octopus | 1 Octopus Deploy | 2019-10-03 | N/A |
| Octopus before 3.17.7 allows attackers to obtain sensitive cleartext information by reading a variable JSON file in certain situations involving Offline Drop Targets. | ||||
| CVE-2018-5706 | 1 Octopus | 1 Octopus Deploy | 2019-10-03 | N/A |
| 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. | ||||
| CVE-2018-4862 | 1 Octopus | 1 Octopus Deploy | 2019-10-03 | N/A |
| 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. | ||||
| CVE-2018-10550 | 1 Octopus | 1 Octopus Deploy | 2019-10-03 | N/A |
| 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. | ||||
| CVE-2017-17665 | 1 Octopus | 1 Octopus Deploy | 2019-10-03 | N/A |
| 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. | ||||
| CVE-2017-15611 | 1 Octopus | 1 Octopus Deploy | 2019-10-03 | N/A |
| 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. | ||||
| CVE-2019-14268 | 1 Octopus | 1 Octopus Deploy | 2019-08-02 | N/A |
| In Octopus Deploy versions 3.0.19 to 2019.7.2, when a web request proxy is configured, an authenticated user (in certain limited circumstances) could trigger a deployment that writes the web request proxy password to the deployment log in cleartext. This is fixed in 2019.7.3. The fix was back-ported to LTS 2019.6.5 as well as LTS 2019.3.7. | ||||