CVE-2024-1250: Restrict group access token creation for custom roles
An issue has been discovered in GitLab EE affecting all versions starting from 16.8 before 16.8.2. When a user is assigned a custom role with managegroupaccesstokens permission, they may be able to create group access tokens with Owner privileges, which may lead to privilege escalation. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N, 6.5). It is now mitigated in the latest release and is assigned CVE-2024-1250.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
GitLab EEto a version that resolves this vulnerability.Fixed in 16.8.2Patch CVE-2024-1250
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2024-1250?
CVE-2024-1250 is considered a high-severity vulnerability due to the potential for privilege escalation.
How do I fix CVE-2024-1250?
To fix CVE-2024-1250, upgrade GitLab EE from any version starting from 16.8 to version 16.8.2 or later.
Which versions of GitLab EE are affected by CVE-2024-1250?
CVE-2024-1250 affects all versions of GitLab EE starting from 16.8 up to, but not including, 16.8.2.
What is the impact of CVE-2024-1250?
The impact of CVE-2024-1250 allows users with a custom role to create group access tokens with Owner privileges, leading to potential privilege escalation.
Who is at risk from CVE-2024-1250?
Organizations using GitLab EE versions between 16.8.0 and 16.8.1 are at risk from CVE-2024-1250 if users are assigned custom roles with manage_group_access_tokens permissions.