CVE ID | Published | Description | Score | Severity |
---|---|---|---|---|
In affected versions of Octopus Deploy it is possible to discover network details via error message | 5.3 |
MEDIUM |
||
In affected versions of Octopus Deploy it is possible to upload a zipbomb file as a task which results in Denial of Service | 5.5 |
MEDIUM |
||
In affected versions of Octopus Deploy it is possible to render user supplied input into the webpage | 5.3 |
MEDIUM |
||
In affected versions of Octopus Deploy it is possible for a user to introduce code via offline package creation | 8.8 |
HIGH |
||
In affected versions of Octopus Deploy it is possible to upload a zipbomb file as a task which results in Denial of Service | 7.5 |
HIGH |
||
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. | 5.3 |
MEDIUM |
||
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. | 9.1 |
CRITICAL |
||
In affected versions of Octopus Server it was identified that the same encryption process was used for both encrypting session cookies and variables. | 5.3 |
MEDIUM |
||
In affected versions of Octopus Deploy it is possible to bypass rate limiting on login using null bytes. | 9.8 |
CRITICAL |
||
In affected versions of Octopus Deploy it is possible to upload a package to built-in feed with insufficient permissions after re-indexing packages. | 6.5 |
MEDIUM |
||
In affected versions of Octopus Deploy it is possible to perform a Regex Denial of Service targeting the build information request validation. | 7.5 |
HIGH |
||
In affected versions of Octopus Deploy it is possible to perform a Regex Denial of Service using the Variable Project Template. | 7.5 |
HIGH |
||
In affected versions of Octopus Deploy it is possible to perform a Regex Denial of Service via the package upload function. | 7.5 |
HIGH |
||
In affected versions of Octopus Deploy, there is no logging of changes to artifacts within Octopus Deploy. | 5.3 |
MEDIUM |
||
When generating a user invitation code in Octopus Server, the validity of this code can be set for a specific number of users. It was possible to bypass this restriction of validity to create extra user accounts above the initial number of invited users. | 7.5 |
HIGH |
||
An issue was discovered in Octopus Deploy 3.4. A deployment target can be configured with an Account or Certificate that is outside the scope of the deployment target. An authorised user can potentially use a certificate that they are not in scope to use. An authorised user is also able to obtain certificate metadata by associating a certificate with certain resources that should fail scope validation. | 4.3 |
MEDIUM |
||
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 other packages or modifying system files. This is a directory traversal in the PackageId value. | 5.7 |
MEDIUM |