Ngalog

**Name of the Vulnerable Software and Affected Versions** GitLab Community and Enterprise Edition versions 11.1.7 and earlier, 11.2.x through 11.2.3, 11.3.x through 11.3.0 **Description** The issue is related to Cross Site Request Forgery (CSRF) in the Slack integration for issuing slash commands. This allows for unauthorized actions to be performed. **Recommendations** For versions 11.1.7 and earlier, update to version 11.1.7 or later. For versions 11.2.x through 11.2.3, update to version 11.2.4 or later. For versions 11.3.x through 11.3.0, update to version 11.3.1 or later.

**Name of the Vulnerable Software and Affected Versions** GitLab Community and Enterprise Edition versions 11.1.7 and earlier, 11.2.x before 11.2.4, 11.3.x before 11.3.1 **Description** The issue is related to Server-Side Request Forgery (SSRF) via the Kubernetes integration. This can lead to the disclosure of a GCP service token. **Recommendations** For versions 11.1.7 and earlier, update to version 11.1.7 or later. For versions 11.2.x before 11.2.4, update to version 11.2.4 or later. For versions 11.3.x before 11.3.1, update to version 11.3.1 or later. As a temporary workaround, consider disabling the Kubernetes integration until a patch is available.

**Name of the Vulnerable Software and Affected Versions** GitLab Community and Enterprise Edition versions 11.1.0 through 11.1.7 GitLab Community and Enterprise Edition versions 11.2.x through 11.2.4 GitLab Community and Enterprise Edition versions 11.3.x through 11.3.1 **Description** An issue allows remote attackers to obtain sensitive information about issues, comments, and project titles via the events API insecure direct object reference. **Recommendations** For versions 11.1.0 through 11.1.7, update to version 11.1.7 or later. For versions 11.2.x through 11.2.4, update to version 11.2.4 or later. For versions 11.3.x through 11.3.1, update to version 11.3.1 or later.

**Name of the Vulnerable Software and Affected Versions** GitLab CE/EE versions 11.3 and later **Description** The issue concerns the endpoint for auto-completing Assignee, which discloses the members of private groups. **Recommendations** For GitLab CE/EE versions 11.3 and later, consider restricting access to the auto-completion endpoint for Assignee to prevent disclosure of private group members until a patch is available.

**Name of the Vulnerable Software and Affected Versions** GitLab EE versions 12.4 through 14.3.6 GitLab EE versions 14.4.0 through 14.4.4 GitLab EE versions 14.5.0 through 14.5.2 **Description** The issue concerns missing authorization, allowing an attacker to access a user's custom project and group templates. **Recommendations** For GitLab EE versions 12.4 through 14.3.6, update to a version outside of this range to resolve the issue. For GitLab EE versions 14.4.0 through 14.4.4, update to a version outside of this range to resolve the issue. For GitLab EE versions 14.5.0 through 14.5.2, update to a version outside of this range to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** GitLab CE/EE versions 11.10 and later **Description** The issue allows an admin of a group to see the SCIM token of that group by visiting a specific endpoint. **Recommendations** For GitLab CE/EE versions 11.10 and later, consider restricting access to the specific endpoint that exposes the SCIM token until a fix is available. As a temporary workaround, consider limiting the privileges of group admins to minimize the risk of exploitation. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

Name of the Vulnerable Software and Affected Versions: GitLab CE/EE versions 11.11 and later Description: The issue allows an attacker to bypass the setting to disable Repo by URL import by making a crafted API call. This affects instances of GitLab CE/EE where this setting is enabled. Recommendations: For GitLab CE/EE versions 11.11 and later, consider disabling the Repo by URL import feature entirely until a patch is available. As a temporary workaround, restrict access to the API endpoint used for the crafted API call to minimize the risk of exploitation. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

Name of the Vulnerable Software and Affected Versions: GitLab CE/EE versions 8.12 and later Description: An authenticated low-privileged malicious user may create a project with unlimited repository size by modifying values in a project export. This issue affects all versions of GitLab CE/EE since version 8.12. Recommendations: For GitLab CE/EE versions 8.12 and later, update to a version that includes a fix for this issue to prevent low-privileged users from creating projects with unlimited repository size.

Name of the Vulnerable Software and Affected Versions: GitLab versions 11.5 and later Description: The issue is related to insufficient validation of authentication parameters in GitLab Pages, allowing an attacker to steal a victim's API token if they click on a maliciously crafted link. Recommendations: For GitLab versions 11.5 and later, update to a version that includes the fix for this issue to prevent API token theft. As a temporary workaround, consider restricting access to GitLab Pages until the issue is resolved. Avoid clicking on suspicious links to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** GitLab versions prior to 13.1 **Description** A vulnerability was discovered that could expose the private activity of a user under certain conditions via the API. **Recommendations** For versions prior to 13.1, update to version 13.1 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** GitLab EE/CE versions 8.0.rc1 through 12.9 **Description** The issue is related to a blind Server-Side Request Forgery (SSRF) in the FogBugz integration. SSRF is a type of attack where an attacker can trick a server into making requests to internal or external systems, potentially leading to unauthorized access or information disclosure. **Recommendations** For GitLab EE/CE versions 8.0.rc1 through 12.9, consider disabling the FogBugz integration as a temporary workaround until a patch is available. Restrict access to the FogBugz module to minimize the risk of exploitation. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** GitLab EE versions 11.6 through 12.8.1 **Description** The issue allows information disclosure by sending a specially crafted request to the "vulnerability feedback" endpoint, potentially exposing a private project namespace. **Recommendations** For GitLab EE versions 11.6 through 12.8.1, consider restricting access to the "vulnerability feedback" endpoint until a fix is available. As a temporary workaround, avoid using the vulnerable endpoint to minimize the risk of information disclosure. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

Name of the Vulnerable Software and Affected Versions: GitLab Community and Enterprise Edition versions 6.8 through 11.11 Description: An issue allows users to bypass the mandatory external authentication provider sign-in restrictions by sending a specially crafted request. This issue is related to Improper Authorization. Recommendations: For GitLab Community and Enterprise Edition versions 6.8 through 11.11, update to a version that includes a fix for this issue to prevent bypassing of mandatory external authentication provider sign-in restrictions.

Name of the Vulnerable Software and Affected Versions: GitLab Enterprise Edition versions 10.6 through 12.0.2 Description: The GitHub project integration in GitLab Enterprise Edition is affected by an SSRF vulnerability, allowing an attacker to make requests to local network resources due to incorrect access control. Recommendations: For GitLab Enterprise Edition versions 10.6 through 12.0.2, update to a version that includes the fix for this issue to prevent exploitation of the SSRF vulnerability in the GitHub project integration.

**Name of the Vulnerable Software and Affected Versions** GitLab EE versions 8.0 through 12.7.2 **Description** The issue is related to incorrect access control. **Recommendations** For GitLab EE versions 8.0 through 12.7.2, update to a version that contains a fix for this issue.

**Name of the Vulnerable Software and Affected Versions** GitLab EE versions 8.14 through 12.5 GitLab EE version 12.4.3 GitLab EE version 12.3.6 **Description** The issue concerns incorrect access control. After a project is changed to private, previously forked repositories can still access information about the private project through the API. **Recommendations** For GitLab EE versions 8.14 through 12.5, consider restricting access to the API until a fix is available. For GitLab EE version 12.4.3, restrict access to the API to minimize the risk of exploitation. For GitLab EE version 12.3.6, avoid using the API to access private project information until the issue is resolved. As a temporary workaround, consider disabling API access to private projects until a patch is available.

Name of the Vulnerable Software and Affected Versions: GitLab Community and Enterprise Edition versions prior to 11.4.13 GitLab Community and Enterprise Edition versions 11.5.x prior to 11.5.6 GitLab Community and Enterprise Edition versions 11.6.x prior to 11.6.1 Description: An issue was discovered that allows Server-Side Request Forgery (SSRF). Recommendations: For versions prior to 11.4.13, update to version 11.4.13 or later. For versions 11.5.x prior to 11.5.6, update to version 11.5.6 or later. For versions 11.6.x prior to 11.6.1, update to version 11.6.1 or later.

Name of the Vulnerable Software and Affected Versions: GitLab Community and Enterprise Edition versions prior to 11.4.13 GitLab Community and Enterprise Edition versions 11.5.x prior to 11.5.6 GitLab Community and Enterprise Edition versions 11.6.x prior to 11.6.1 Description: The issue is related to Incorrect Access Control. Recommendations: For GitLab Community and Enterprise Edition versions prior to 11.4.13, update to version 11.4.13 or later. For GitLab Community and Enterprise Edition versions 11.5.x prior to 11.5.6, update to version 11.5.6 or later. For GitLab Community and Enterprise Edition versions 11.6.x prior to 11.6.1, update to version 11.6.1 or later.

**Name of the Vulnerable Software and Affected Versions** GitLab CE/EE versions prior to 12.3.2 GitLab CE/EE versions prior to 12.2.6 GitLab CE/EE versions prior to 12.1.12 **Description** A authentication bypass vulnerability exists in the Salesforce login integration that could be used by an attacker to create an account that bypassed domain restrictions and email verification requirements. **Recommendations** For versions prior to 12.3.2, update to version 12.3.2 or later. For versions prior to 12.2.6, update to version 12.2.6 or later. For versions prior to 12.1.12, update to version 12.1.12 or later.

**Name of the Vulnerable Software and Affected Versions** GitLab Community and Enterprise Edition versions 11.5.8 and earlier, 11.6.x before 11.6.6, 11.7.x before 11.7.1 **Description** The issue allows information disclosure due to an authorization problem, enabling the contributed project information of a private profile to be viewed. **Recommendations** For versions 11.5.8 and earlier, update to version 11.5.8 or later. For versions 11.6.x before 11.6.6, update to version 11.6.6 or later. For versions 11.7.x before 11.7.1, update to version 11.7.1 or later.