Octopus Server
by Octopus
CVEs (16)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2023-1904 | 0.00 | — | 0.00 | Dec 14, 2023 | 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. | |||
| CVE-2022-4898 | 0.00 | — | 0.00 | Jan 31, 2023 | 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… | |||
| CVE-2022-3614 | 0.00 | — | 0.00 | Jan 3, 2023 | 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. | |||
| CVE-2022-2721 | 0.00 | — | 0.00 | Nov 25, 2022 | 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 enabled. | |||
| CVE-2022-2572 | 0.00 | — | 0.00 | Nov 1, 2022 | 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. | |||
| CVE-2022-2508 | 0.00 | — | 0.00 | Oct 27, 2022 | 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. | |||
| CVE-2022-2782 | 0.00 | — | 0.00 | Oct 26, 2022 | 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. | |||
| CVE-2022-2780 | 0.00 | — | 0.00 | Oct 14, 2022 | 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. | |||
| CVE-2022-2828 | 0.00 | — | 0.00 | Oct 13, 2022 | 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 | |||
| CVE-2022-2720 | 0.00 | — | 0.00 | Oct 12, 2022 | 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. | |||
| CVE-2021-26556 | 0.00 | — | 0.00 | Oct 7, 2021 | 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 access. | |||
| CVE-2021-31820 | 0.00 | — | 0.00 | Aug 18, 2021 | 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. | |||
| CVE-2021-31817 | 0.00 | — | 0.00 | Jul 8, 2021 | When configuring Octopus Server if it is configured with an external SQL database, on initial configuration the database password is written to the OctopusServer.txt log file in plaintext. | |||
| CVE-2021-31816 | 0.00 | — | 0.00 | Jul 8, 2021 | When configuring Octopus Server if it is configured with an external SQL database, on initial configuration the database password is written to the OctopusServer.txt log file in plaintext. | |||
| CVE-2021-31818 | 0.00 | — | 0.00 | Jun 17, 2021 | Affected versions of Octopus Server are prone to an authenticated SQL injection vulnerability in the Events REST API because user supplied data in the API request isn’t parameterised correctly. Exploiting this vulnerability could allow unauthorised access to database tables. | |||
| CVE-2021-30183 | 0.00 | — | 0.00 | May 14, 2021 | Cleartext storage of sensitive information in multiple versions of Octopus Server where in certain situations when running import or export processes, the password used to encrypt and decrypt sensitive values would be written to the logs in plaintext. |
- CVE-2023-1904Dec 14, 2023risk 0.00cvss —epss 0.00
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.
- CVE-2022-4898Jan 31, 2023risk 0.00cvss —epss 0.00
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…
- CVE-2022-3614Jan 3, 2023risk 0.00cvss —epss 0.00
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.
- CVE-2022-2721Nov 25, 2022risk 0.00cvss —epss 0.00
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 enabled.
- CVE-2022-2572Nov 1, 2022risk 0.00cvss —epss 0.00
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.
- CVE-2022-2508Oct 27, 2022risk 0.00cvss —epss 0.00
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.
- CVE-2022-2782Oct 26, 2022risk 0.00cvss —epss 0.00
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.
- CVE-2022-2780Oct 14, 2022risk 0.00cvss —epss 0.00
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.
- CVE-2022-2828Oct 13, 2022risk 0.00cvss —epss 0.00
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
- CVE-2022-2720Oct 12, 2022risk 0.00cvss —epss 0.00
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.
- CVE-2021-26556Oct 7, 2021risk 0.00cvss —epss 0.00
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 access.
- CVE-2021-31820Aug 18, 2021risk 0.00cvss —epss 0.00
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.
- CVE-2021-31817Jul 8, 2021risk 0.00cvss —epss 0.00
When configuring Octopus Server if it is configured with an external SQL database, on initial configuration the database password is written to the OctopusServer.txt log file in plaintext.
- CVE-2021-31816Jul 8, 2021risk 0.00cvss —epss 0.00
When configuring Octopus Server if it is configured with an external SQL database, on initial configuration the database password is written to the OctopusServer.txt log file in plaintext.
- CVE-2021-31818Jun 17, 2021risk 0.00cvss —epss 0.00
Affected versions of Octopus Server are prone to an authenticated SQL injection vulnerability in the Events REST API because user supplied data in the API request isn’t parameterised correctly. Exploiting this vulnerability could allow unauthorised access to database tables.
- CVE-2021-30183May 14, 2021risk 0.00cvss —epss 0.00
Cleartext storage of sensitive information in multiple versions of Octopus Server where in certain situations when running import or export processes, the password used to encrypt and decrypt sensitive values would be written to the logs in plaintext.