Rohit Shambhuni

**Name of the Vulnerable Software and Affected Versions** GitLab CE/EE versions 17.5 through 18.4.5 GitLab CE/EE versions 18.5 through 18.5.3 GitLab CE/EE versions 18.6 through 18.6.1 **Description** An authenticated user could potentially discover the names of private projects they do not have access to through API requests. The issue affects GitLab CE/EE. **Recommendations** Update GitLab CE/EE to version 18.4.6 or later. Update GitLab CE/EE to version 18.5.4 or later. Update GitLab CE/EE to version 18.6.2 or later.

Name of the Vulnerable Software and Affected Versions: GitLab EE versions 16.8 through 16.8.2 Description: The issue is related to insecure privilege management in GitLab EE. When a user is assigned a custom role with the `manage group access tokens` permission, they may be able to create group access tokens with Owner privileges, leading to privilege escalation. This could allow a remote attacker to elevate their privileges. Recommendations: For GitLab EE versions 16.8 through 16.8.2, consider disabling the custom role with the `manage group access tokens` permission until a patch is available to prevent potential privilege escalation. Restrict access to group access tokens to minimize the risk of exploitation. Avoid assigning the `manage group access tokens` permission to users who do not require it. At the moment, there is no information about a newer version that contains a fix for this vulnerability.