CPE Details
Octopus Server 2022.1.2803
2022.1.2803
2022-07-27
15h09 +00:00
15h09 +00:00
2022-07-27
15h20 +00:00
15h20 +00:00
Alerte pour un CPE
Restez informé de toutes modifications pour un CPE spécifique.
CPE Name: cpe:2.3:a:octopus:octopus_server:2022.1.2803:*:*:*:*:*:*:*
Informations
Vendor
octopusProduct
octopus_serverVersion
2022.1.2803Related CVE
| CVE ID | Publié | Description | Score | Gravité |
|---|---|---|---|---|
| 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. | 7.5 |
Haute |
||
| 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. | 5.5 |
Moyen |
||
| In affected versions of Octopus Deploy it is possible for a low privileged guest user to interact with extension endpoints. | 5.5 |
Moyen |
||
| In affected versions of Octopus Deploy it is possible to discover network details via error message | 5.3 |
Moyen |
||
| 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 |
Moyen |
||
| In affected versions of Octopus Deploy it is possible to render user supplied input into the webpage | 5.3 |
Moyen |
||
| In affected versions of Octopus Deploy it is possible for a user to introduce code via offline package creation | 8.8 |
Haute |
||
| In affected versions of Octopus Deploy it is possible for a user to view Tagsets without being explicitly assigned permissions to view these items | 4.3 |
Moyen |
||
| In affected versions of Octopus Deploy it is possible for a user to view Workerpools without being explicitly assigned permissions to view these items | 4.3 |
Moyen |
||
| 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 |
Haute |
||
| 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 | 5.4 |
Moyen |
||
| 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. | 6.1 |
Moyen |
||
| In affected versions of Octopus Deploy it is possible for certain types of sensitive variables to inadvertently become unmasked when viewed in variable preview. | 7.5 |
Haute |
||
| 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 valid after the access was revoked. | 9.8 |
Critique |
||
| 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 |
Moyen |
||
| 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 |
Critique |
||
| 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 NTLM relay attack. | 8.1 |
Haute |
||
| 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 | 6.5 |
Moyen |
||
| 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. | 5.3 |
Moyen |
||
| 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 |
Moyen |
||
| In affected versions of Octopus Server it was identified that a session cookie could be used as the CSRF token | 5.3 |
Moyen |
||
| In affected versions of Octopus Deploy it is possible to bypass rate limiting on login using null bytes. | 9.8 |
Critique |
||
| In affected versions of Octopus Deploy it is possible to reveal the Space ID of spaces that the user does not have access to view in an error message when a resource is part of another Space. | 4.3 |
Moyen |
||
| 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 |
Moyen |
||
| In affected versions of Octopus Deploy it is possible to perform a Regex Denial of Service targeting the build information request validation. | 7.5 |
Haute |
||
| In affected versions of Octopus Deploy it is possible to perform a Regex Denial of Service using the Variable Project Template. | 7.5 |
Haute |
||
| In affected versions of Octopus Deploy it is possible to perform a Regex Denial of Service via the package upload function. | 7.5 |
Haute |
||
| In affected versions of Octopus Deploy it is possible to unmask sensitive variables by using variable preview. | 5.3 |
Moyen |
||
| In affected versions of Octopus Deploy, there is no logging of changes to artifacts within Octopus Deploy. | 5.3 |
Moyen |
||
| In affected versions of Octopus Server the help sidebar can be customized to include a Cross-Site Scripting payload in the support link. | 6.1 |
Moyen |
||
| 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 not have permissions to access. This vulnerability only impacts projects within the same Space. | 5.3 |
Moyen |
2025©
tesweb SA
