Joaxcaron

**Name of the Vulnerable Software and Affected Versions** GitLab EE/CE versions 16.6 through 17.9.7 GitLab EE/CE versions 17.10 through 17.10.5 GitLab EE/CE versions 17.11 through 17.11.1 **Description** An issue has been discovered in GitLab EE/CE that could allow an attacker to track users' browsing activities, potentially leading to full account take-over. **Recommendations** For versions 16.6 through 17.9.7, update to version 17.9.7 or later. For versions 17.10 through 17.10.5, update to version 17.10.5 or later. For versions 17.11 through 17.11.1, update to version 17.11.1 or later.

**Name of the Vulnerable Software and Affected Versions** GitLab CE/EE versions 16.1 through 17.4.6 GitLab CE/EE versions 17.5 through 17.5.4 GitLab CE/EE versions 17.6 through 17.6.2 **Description** An issue was discovered in GitLab CE/EE where the injection of Network Error Logging (NEL) headers in the k8s proxy response could lead to session data exfiltration. This could potentially allow an attacker to gain unauthorized access to accounts. The issue is related to the disclosure of information during data transmission. **Recommendations** For GitLab CE/EE versions 16.1 through 17.4.6, update to version 17.4.6 or later. For GitLab CE/EE versions 17.5 through 17.5.4, update to version 17.5.4 or later. For GitLab CE/EE versions 17.6 through 17.6.2, update to version 17.6.2 or later. As a temporary workaround, consider restricting access to the k8s proxy response to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** GitLab CE/EE versions 16.0 through 17.3.6 GitLab CE/EE versions 17.4.0 through 17.4.3 GitLab CE/EE versions 17.5.0 through 17.5.1 **Description** The issue allows an attacker to inject malicious JavaScript code in Analytics Dashboards through a specially crafted URL. This could be exploited by a remote attacker to inject arbitrary JavaScript code. **Recommendations** For GitLab CE/EE versions 16.0 through 17.3.6, update to version 17.3.7 or later. For GitLab CE/EE versions 17.4.0 through 17.4.3, update to version 17.4.4 or later. For GitLab CE/EE versions 17.5.0 through 17.5.1, update to version 17.5.2 or later.

**Name of the Vulnerable Software and Affected Versions** GitLab CE/EE versions 17.2 through 17.3.7 GitLab CE/EE versions 17.4 through 17.4.4 GitLab CE/EE versions 17.5 through 17.5.2 **Description** The issue is related to the incorrect limitation of visible layers in the user interface of the GitLab CE/EE platform, which could allow a remote attacker to gain unauthorized access to the API via the Device OAuth flow. This could potentially allow an attacker to gain full API access as the victim. **Recommendations** For GitLab CE/EE versions 17.2 through 17.3.7, update to version 17.3.7 or later. For GitLab CE/EE versions 17.4 through 17.4.4, update to version 17.4.4 or later. For GitLab CE/EE versions 17.5 through 17.5.2, update to version 17.5.2 or later. As a temporary workaround, consider restricting access to the Device OAuth flow until a patch is available.

Name of the Vulnerable Software and Affected Versions: GitLab CE/EE versions 15.10 through 17.3.5 GitLab CE/EE versions 17.4 through 17.4.2 GitLab CE/EE versions 17.5 through 17.5.0 Description: An issue has been discovered in GitLab CE/EE that could allow an attacker to inject HTML into the Global Search field on a diff view, leading to cross-site scripting (XSS) attacks. This is related to the lack of protection measures for the web page structure, which could enable a remote attacker to conduct inter-site script attacks. Recommendations: For GitLab CE/EE versions 15.10 through 17.3.5, update to version 17.3.6 or later. For GitLab CE/EE versions 17.4 through 17.4.2, update to version 17.4.3 or later. For GitLab CE/EE versions 17.5 through 17.5.0, update to version 17.5.1 or later. As a temporary workaround, consider restricting access to the Global Search field on diff views until a patch is available.

**Name of the Vulnerable Software and Affected Versions** GitLab versions 15.2 through 17.4.6 GitLab versions 17.5 through 17.5.4 GitLab versions 17.6 through 17.6.2 **Description** The issue is related to a problem in GitLab that allows for a Cross-Site Request Forgery (CSRF) attack. This can be exploited by a remote attacker to leak the anti-CSRF token to an external site when the Harbor integration is enabled. The issue affects self-hosted installations of GitLab. **Recommendations** For GitLab versions 15.2 through 17.4.6, update to a version later than 17.4.6 to resolve the issue. For GitLab versions 17.5 through 17.5.4, update to a version later than 17.5.4 to resolve the issue. For GitLab versions 17.6 through 17.6.2, update to a version later than 17.6.2 to resolve the issue. As a temporary workaround, consider disabling the Harbor integration until a patch is available.

**Name of the Vulnerable Software and Affected Versions** GitLab EE versions 15.10 through 17.2.8 GitLab EE versions 17.3 through 17.3.4 GitLab EE versions 17.4 through 17.4.1 **Description** An issue has been discovered in GitLab EE that could allow a remote attacker to perform a Server-Side Request Forgery (SSRF) attack. This issue is related to insufficient validation of incoming requests. Instances with the Product Analytics Dashboard configured and enabled are vulnerable to SSRF attacks. **Recommendations** For GitLab EE versions 15.10 through 17.2.8, upgrade to version 17.2.9. For GitLab EE versions 17.3 through 17.3.4, upgrade to version 17.3.5. For GitLab EE versions 17.4 through 17.4.1, upgrade to version 17.4.2. As a temporary workaround, consider disabling the Product Analytics Dashboard until a patch is available. Restrict access to the Product Analytics Dashboard to minimize the risk of exploitation.

Name of the Vulnerable Software and Affected Versions: GitLab EE versions 16.0 through 17.2.7 GitLab EE versions 17.3 through 17.3.3 GitLab EE versions 17.4 through 17.4.0 Description: An issue has been discovered in GitLab EE affecting the AI feature, which reads unsanitized content. This could have allowed an attacker to hide prompt injection, potentially impacting data integrity. The vulnerability is related to a lack of output encoding or sanitization mechanism in the AI feature of the GitLab platform. Recommendations: For GitLab EE versions 16.0 through 17.2.7, update to version 17.2.8 or later. For GitLab EE versions 17.3 through 17.3.3, update to version 17.3.4 or later. For GitLab EE versions 17.4 through 17.4.0, update to version 17.4.1 or later. As a temporary workaround, consider disabling the AI feature until a patch is available. Restrict access to the AI feature to minimize the risk of exploitation. Avoid using the AI feature in sensitive environments until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** GitLab CE/EE versions 1.0 through 17.0.6 GitLab CE/EE versions 17.1 through 17.1.4 GitLab CE/EE versions 17.2 through 17.2.2 **Description** A Denial of Service (DoS) condition has been discovered in GitLab CE/EE, allowing an attacker to cause resource exhaustion via the `banzai pipeline`. This issue affects multiple versions of the software and can be exploited by a remote attacker to cause a service disruption. **Recommendations** For versions 1.0 through 17.0.6, update to a version later than 17.0.6. For versions 17.1 through 17.1.4, update to a version later than 17.1.4. For versions 17.2 through 17.2.2, update to a version later than 17.2.2. As a temporary workaround, consider restricting access to the `banzai pipeline` to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** GitLab versions 17.1 through 17.2.9 GitLab versions 17.3 through 17.3.5 GitLab versions 17.4 through 17.4.2 **Description** A cross-site scripting issue has been discovered in GitLab. The issue is related to the lack of protection of the web page structure, which can allow a remote attacker to conduct an XSS attack. When adding or authorizing an application, it can be made to render as HTML under specific circumstances. **Recommendations** For GitLab versions 17.1 through 17.2.9, update to version 17.2.9 or later to resolve the issue. For GitLab versions 17.3 through 17.3.5, update to version 17.3.5 or later to resolve the issue. For GitLab versions 17.4 through 17.4.2, update to version 17.4.2 or later to resolve the issue. As a temporary workaround, consider restricting the rendering of HTML when adding or authorizing applications to minimize the risk of exploitation.

Name of the Vulnerable Software and Affected Versions: GitLab EE versions 16.0 through 16.11.4 GitLab EE versions 17.0 through 17.0.2 GitLab EE versions 17.1 through 17.1.0 Description: The issue allows an attacker to access issues and epics without having an SSO session using Duo Chat. This is related to insufficient protection of service data in the Single sign-on (SSO) authentication mechanism of the GitLab Duo Chat web interface. The exploitation of this issue may allow a remote attacker to gain unauthorized access to protected information using Epics and Issues modules. Recommendations: For versions 16.0 through 16.11.4, update to version 16.11.5 or later. For versions 17.0 through 17.0.2, update to version 17.0.3 or later. For versions 17.1 through 17.1.0, update to version 17.1.1 or later. As a temporary workaround, consider disabling the Duo Chat functionality until a patch is available. Restrict access to the Epics and Issues modules to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** GitLab CE/EE versions 8.4 through 16.10.7 GitLab CE/EE versions 16.11 through 16.11.4 GitLab CE/EE versions 17.0 through 17.0.2 **Description** A vulnerability in GitLab's Asana integration allowed an attacker to potentially cause a regular expression denial of service by sending specially crafted requests. This issue is related to uncontrolled resource consumption, which can be exploited by a remote attacker to cause a denial of service using specially crafted requests. **Recommendations** For versions 8.4 through 16.10.7, update to version 16.10.7 or later. For versions 16.11 through 16.11.4, update to version 16.11.4 or later. For versions 17.0 through 17.0.2, update to version 17.0.2 or later. As a temporary workaround, consider disabling the Asana integration until a patch is available.

**Name of the Vulnerable Software and Affected Versions** GitLab CE/EE versions 13.1 through 16.10.7 GitLab CE/EE versions 16.11 through 16.11.4 GitLab CE/EE versions 17.0 through 17.0.2 **Description** An issue has been discovered in GitLab CE/EE that allows an attacker to cause a denial of service using maliciously crafted files. This is related to an uncontrolled resource consumption. The exploitation of this issue may allow a remote attacker to cause a denial of service. **Recommendations** For versions 13.1 through 16.10.7, update to version 16.10.7 or later to resolve the issue. For versions 16.11 through 16.11.4, update to version 16.11.4 or later to resolve the issue. For versions 17.0 through 17.0.2, update to version 17.0.2 or later to resolve the issue. As a temporary workaround, consider restricting the upload of files to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** GitLab CE/EE versions prior to 16.10.7 GitLab CE/EE versions 16.11 prior to 16.11.4 GitLab CE/EE versions 17.0 prior to 17.0.2 **Description** A vulnerability in GitLab's CI/CD pipeline editor could allow for denial of service attacks through maliciously crafted configuration files. This issue is related to uncontrolled resource consumption, which can be exploited by a remote attacker to cause a denial of service using specially crafted malicious files. **Recommendations** For versions prior to 16.10.7, update to version 16.10.7 or later. For versions 16.11 prior to 16.11.4, update to version 16.11.4 or later. For versions 17.0 prior to 17.0.2, update to version 17.0.2 or later. As a temporary workaround, consider restricting access to the CI/CD pipeline editor to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** GitLab versions 5.1 through 16.10.7 GitLab versions 16.11 through 16.11.4 GitLab versions 17.0 through 17.0.2 **Description** A cross-site scripting issue has been discovered in GitLab. When viewing an XML file in a repository in raw mode, it can be made to render as HTML if viewed under specific circumstances. **Recommendations** For versions 5.1 through 16.10.7, update to version 16.10.7 or later. For versions 16.11 through 16.11.4, update to version 16.11.4 or later. For versions 17.0 through 17.0.2, update to version 17.0.2 or later.

**Name of the Vulnerable Software and Affected Versions** GitLab versions 5.1 through 17.0.6 GitLab versions 17.1 through 17.1.4 GitLab versions 17.2 through 17.2.2 **Description** A cross-site scripting issue exists due to inadequate protection of the web page structure. This can be exploited by a remote attacker to conduct an XSS attack by sending a specially crafted XML file. The issue arises when viewing an XML file in a repository in raw mode under specific circumstances, allowing it to render as HTML. **Recommendations** For versions 5.1 through 17.0.6, update to a version after 17.0.6 to resolve the issue. For versions 17.1 through 17.1.4, update to a version after 17.1.4 to resolve the issue. For versions 17.2 through 17.2.2, update to a version after 17.2.2 to resolve the issue. As a temporary workaround, consider restricting access to viewing XML files in raw mode until a patch is available.

Name of the Vulnerable Software and Affected Versions: GitLab CE/EE versions 12.0 through 16.11.5 GitLab CE/EE versions 17.0 through 17.0.3 GitLab CE/EE versions 17.1 through 17.1.1 Description: An issue in GitLab CE/EE allows an attacker to cause a denial of service using a crafted OpenAPI file, which can lead to uncontrolled resource consumption. This can be exploited by a remote attacker to disrupt service. Recommendations: For versions 12.0 through 16.11.5, update to version 16.11.5 or later to resolve the issue. For versions 17.0 through 17.0.3, update to version 17.0.3 or later to resolve the issue. For versions 17.1 through 17.1.1, update to version 17.1.1 or later to resolve the issue. As a temporary workaround, consider restricting access to the OpenAPI file to minimize the risk of exploitation.

Name of the Vulnerable Software and Affected Versions: GitLab CE/EE versions 16.3 through 16.11.4 GitLab CE/EE versions 17.0 through 17.0.2 GitLab CE/EE versions 17.1 through 17.1.0 Description: A Cross Window Forgery issue exists within GitLab CE/EE due to an incorrect restriction of visualizable layers in the user interface. This allows an attacker to abuse the OAuth authentication flow via a crafted payload, potentially leading to unauthorized actions. Recommendations: For versions 16.3 through 16.11.4, update to version 16.11.5 or later. For versions 17.0 through 17.0.2, update to version 17.0.3 or later. For versions 17.1 through 17.1.0, update to version 17.1.1 or later. As a temporary workaround, consider restricting access to the OAuth authentication flow until a patch is available.

Name of the Vulnerable Software and Affected Versions: GitLab CE/EE versions 9.2 through 16.11.5 GitLab CE/EE versions 17.0 through 17.0.3 GitLab CE/EE versions 17.1 through 17.1.1 Description: The issue concerns the processing logic for generating links in dependency files, which can lead to a regular expression Denial of Service (DoS) attack on the server. This is due to the use of a regular expression with inefficient computational complexity. The exploitation of this issue can allow a remote attacker to cause a denial of service. Recommendations: For GitLab CE/EE versions 9.2 through 16.11.5, update to version 16.11.5 or later. For GitLab CE/EE versions 17.0 through 17.0.3, update to version 17.0.3 or later. For GitLab CE/EE versions 17.1 through 17.1.1, update to version 17.1.1 or later. As a temporary workaround, consider restricting the processing of dependency files to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** GitLab EE versions 11.3 through 16.6.7 GitLab EE versions 16.7 through 16.7.5 GitLab EE versions 16.8 through 16.8.2 GitLab EE versions 16.9 through 16.9.1 **Description** The issue is related to the CODEOWNERS component of the GitLab platform, which is vulnerable to uncontrolled resource consumption. This can be exploited by a remote attacker to cause a denial of service. The exploitation involves using maliciously crafted content in the CODEOWNERS file to cause a client-side denial of service. **Recommendations** For GitLab EE versions 11.3 through 16.6.7, update to a version after 16.6.7 to resolve the issue. For GitLab EE versions 16.7 through 16.7.5, update to a version after 16.7.5 to resolve the issue. For GitLab EE versions 16.8 through 16.8.2, update to a version after 16.8.2 to resolve the issue. For GitLab EE versions 16.9 through 16.9.1, update to a version after 16.9.1 to resolve the issue. As a temporary workaround, consider restricting access to the CODEOWNERS file to minimize the risk of exploitation.