SQL Injection in the Octopus Server REST API

In affected versions of Octopus Server where access is managed by an external authentication provider, it was possible that the API key/keys of a disabled/deleted user were still…

In affected versions of Octopus Deploy it is possible to bypass rate limiting on login using null bytes

In Octopus Deploy 2018.4.4 through 2018.5.1, Octopus variables that are sourced from the target do not have sensitive values obfuscated in the deployment logs

In affected version of Octopus Deploy it was possible to remove files and/or contents of files on the host using an API endpoint

In affected versions of Octopus Server it is possible for a session token to be valid indefinitely due to improper validation of the session token parameters

In affected Microsoft Windows versions of Octopus Deploy, the server can be coerced into sending server-side requests that contain authentication material allowing a suitably…

In affected versions of Octopus Deploy it is possible for a user to introduce code via offline package creation

In Octopus Deploy 2018.8.0 through 2018.9.x before 2018.9.1, an authenticated user with permission to modify deployment processes could upload a maliciously crafted YAML…

In affected versions of Octopus Server it is possible to use the Git Connectivity test function on the VCS project to initiate an SMB request resulting in the potential for an…

In Octopus Deploy 2019.1.0 through 2019.3.1 and 2019.4.0 through 2019.4.5, an authenticated user with the VariableViewUnscoped or VariableEditUnscoped permission scoped to a…

When Octopus Server is installed using a custom folder location, folder ACLs are not set correctly and could lead to an unprivileged user using DLL side-loading to gain privileged…

In affected versions of Octopus Server under certain circumstances it is possible for sensitive variables to be printed in the deployment variable snapshot in clear-text

In affected versions of Octopus Server the preview import feature could be leveraged to identify the existence of a target file

A race condition was identified through which privilege escalation was possible in certain configurations

In affected versions of Octopus Server it is possible for the OpenID client secret to be logged in clear text during the configuration of Octopus Server

In affected versions of Octopus Deploy it is possible to upload a zipbomb file as a task which results in Denial of Service

In affected versions of Octopus Deploy it is possible for certain types of sensitive variables to inadvertently become unmasked when viewed in variable preview

In affected versions of Octopus Server it is possible for target discovery to print certain values marked as sensitive to log files in plaint-text in when verbose logging is…

In affected versions of Octopus Deploy it is possible to perform a Regex Denial of Service targeting the build information request validation

In affected versions of Octopus Deploy it is possible to perform a Regex Denial of Service using the Variable Project Template

In affected versions of Octopus Deploy it is possible to perform a Regex Denial of Service via the package upload function

When generating a user invitation code in Octopus Server, the validity of this code can be set for a specific number of users

In Octopus Server after version 2018.8.2 if the Octopus Server Web Request Proxy is configured with authentication, the password is shown in plaintext in the UI

In Octopus Deploy version 2018.5.1 to 2018.5.7, a user with Task View is able to view a password for a Service Fabric Cluster, when the Service Fabric Cluster target is configured…

In affected versions of Octopus Server, permissions were not checked correctly resulting in any authenticated user being able to make server level changes using a certain API…

In affected versions of Octopus Server under certain circumstances it is possible for sensitive variables to be printed in the task log in clear-text

In affected versions of Octopus Server it is possible to reveal information about teams via the API due to an Insecure Direct Object Reference (IDOR) vulnerability

In affected versions of Octopus Deploy it is possible to upload a package to built-in feed with insufficient permissions after re-indexing packages

An Information Exposure issue in the Terraform deployment step in Octopus Deploy before 2019.1.8 (and before 2018.10.4 LTS) allows remote authenticated users to view sensitive…

In affected versions of Octopus Deploy users of certain browsers using AD to sign-in to Octopus Server were able to bypass authentication checks and be redirected to the…

In affected versions of Octopus Server the help sidebar can be customized to include a Cross-Site Scripting payload in the support link

In affected Octopus Server versions when the server HTTP and HTTPS bindings are configured to localhost, Octopus Server will allow open redirects

In Octopus Deploy 3.x before 3.15.4, an authenticated user with PackagePush permission to upload packages could upload a maliciously crafted NuGet package, potentially overwriting…

In affected versions of Octopus Deploy it is possible to upload a zipbomb file as a task which results in Denial of Service

In affected versions of Octopus Server error messages were handled unsafely on the error page

In affected versions of Octopus Deploy it was possible to upload files to unexpected locations on the host using an API endpoint

In affected versions of Octopus Server with certain access levels it was possible to embed a Cross-Site Scripting payload on the audit page

In affected versions of Octopus Server the help sidebar can be customized to include a Cross-Site Scripting payload in the support link

In affected versions of Octopus Deploy where customers are using Active Directory for authentication it was possible for an unauthenticated user to make an API request against two…

In affected versions of Octopus Deploy it is possible to discover network details via error message

In affected versions of Octopus Deploy it is possible to render user supplied input into the webpage

In affected versions of Octopus Server it is possible to reveal the existence of resources in a space that the user does not have access to due to verbose error messaging

In affected versions of Octopus Server it was identified that when a sensitive value is a substring of another value, sensitive value masking will only partially work

In affected versions of Octopus Server it was identified that a session cookie could be used as the CSRF token

In affected versions of Octopus Server it was identified that the same encryption process was used for both encrypting session cookies and variables

In affected versions of Octopus Deploy it is possible to unmask sensitive variables by using variable preview

In affected versions of Octopus Deploy, there is no logging of changes to artifacts within Octopus Deploy

In affected versions of Octopus Server an Insecure Direct Object Reference vulnerability exists where it is possible for a user to download Project Exports from a Project they do…

In affected versions of Octopus Deploy Insufficient checks on the project trigger actions allows an unauthorized user to trigger a deployment