Filtered by vendor Octopus
Subscribe
Total
76 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2020-24566 | 1 Octopus | 1 Octopus Deploy | 2020-09-10 | 4.3 MEDIUM | 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-2018-9039 | 1 Octopus | 1 Octopus Deploy | 2020-08-24 | 4.0 MEDIUM | 6.5 MEDIUM |
| 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-19375 | 1 Octopus | 1 Octopus Deploy | 2020-08-24 | 4.3 MEDIUM | 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-2019-19084 | 1 Octopus | 1 Octopus Deploy | 2019-11-20 | 4.0 MEDIUM | 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-2018-12884 | 1 Octopus | 1 Octopus Deploy | 2019-10-02 | 4.0 MEDIUM | 6.5 MEDIUM |
| In Octopus Deploy 3.0 onwards (before 2018.6.7), an authenticated user with incorrect permissions may be able to create Accounts under the Infrastructure menu. | |||||
| CVE-2018-5706 | 1 Octopus | 1 Octopus Deploy | 2019-10-02 | 6.5 MEDIUM | 8.8 HIGH |
| 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-02 | 6.5 MEDIUM | 8.8 HIGH |
| 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-2017-15609 | 1 Octopus | 1 Octopus Deploy | 2019-10-02 | 5.0 MEDIUM | 7.5 HIGH |
| 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-10550 | 1 Octopus | 1 Octopus Deploy | 2019-10-02 | 5.0 MEDIUM | 7.5 HIGH |
| 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-02 | 6.5 MEDIUM | 8.8 HIGH |
| 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-02 | 4.0 MEDIUM | 6.5 MEDIUM |
| 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 | 4.0 MEDIUM | 6.5 MEDIUM |
| 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. | |||||
| CVE-2018-10581 | 1 Octopus | 1 Octopus Deploy | 2018-06-13 | 5.5 MEDIUM | 5.4 MEDIUM |
| In Octopus Deploy 3.4.x before 2018.4.7, an authenticated user is able to view/update/save variable values within the Tenant Variables area for Environments that do not exist within their associated Team scoping. This occurs in situations where this authenticated user also belongs to multiple teams, where one of the Teams has the VariableEdit permission or VariableView permissions for the Environment. | |||||
| CVE-2017-16801 | 1 Octopus | 1 Octopus Deploy | 2017-12-01 | 3.5 LOW | 5.4 MEDIUM |
| Cross-site scripting (XSS) vulnerability in Octopus Deploy 3.7.0-3.17.13 (fixed in 3.17.14) allows remote authenticated users to inject arbitrary web script or HTML via the Step Template Name parameter. | |||||
| CVE-2017-16810 | 1 Octopus | 1 Octopus Deploy | 2017-11-30 | 3.5 LOW | 5.4 MEDIUM |
| Cross-site scripting (XSS) vulnerability in the All Variables tab in Octopus Deploy 3.4.0-3.13.6 (fixed in 3.13.7) allows remote attackers to inject arbitrary web script or HTML via the Variable Set Name parameter. | |||||
| CVE-2017-15610 | 1 Octopus | 1 Octopus Deploy | 2017-10-25 | 4.0 MEDIUM | 6.5 MEDIUM |
| An issue was discovered in Octopus before 3.17.7. When the special Guest user account is granted the CertificateExportPrivateKey permission, and Guest Access is enabled for the Octopus Server, an attacker can sign in as the Guest account and export Certificates managed by Octopus, including the private key. | |||||