| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| 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 Deploy users of certain browsers using AD to sign-in to Octopus Server were able to bypass authentication checks and be redirected to the configured redirect url without any validation. |
| In affected versions of Octopus Server the help sidebar can be customized to include a Cross-Site Scripting payload in the support link. This was initially resolved in advisory 2022-07 however it was identified that the fix could be bypassed in certain circumstances. A different approach was taken to prevent the possibility of the support link being susceptible to XSS |
| 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 a user to view Workerpools without being explicitly assigned permissions to view these items |
| In affected versions of Octopus Deploy it is possible for a user to view Tagsets without being explicitly assigned permissions to view these items |
| In affected versions of Octopus Deploy it is possible for a user to introduce code via offline package creation |
| In affected versions of Octopus Deploy it is possible to render user supplied input into the webpage |
| 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 to discover network details via error message |
| 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, there is no logging of changes to artifacts within Octopus Deploy. |
| 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 upload a package to built-in feed with insufficient permissions after re-indexing packages. |
| 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. |
| 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. |