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 Server with certain access levels it was possible to embed a Cross-Site Scripting Payload via artifacts

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 with the LDAP authentication provider enabled, any authenticated user could call the LDAP user search and LDAP group search

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 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 the same encryption process was used for both encrypting session cookies and variables

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, a user with permission to upload a malicious nuget package is able to deploy a script step so the script executes outside of the parent…

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

In affected versions of Octopus Server it was possible for a user with sufficient access to set custom headers in all server responses

In affected versions of Octopus Server it was possible for a low privileged user to manipulate an API request to change the signing key expiration and revocation time frames via…

In affected versions of Octopus Server it was possible to create a new API key from an existing access token resulting in the new API key having a lifetime exceeding the original…

It is possible for an API key to be logged in clear text in the audit log file after an invalid login attempt

In affected versions of Octopus Deploy it is possible for a low privileged guest user to craft a request that allows enumeration/recon of an environment

In affected versions of Octopus Deploy it is possible for a low privileged guest user to interact with extension endpoints