CVE-2024-1299: Privilege Chaining in GitLab
A privilege escalation vulnerability was discovered in GitLab affecting versions 16.8 prior to 16.8.4 and 16.9 prior to 16.9.2. It was possible for a user with custom role of managegroupaccesstokens to rotate group access tokens with owner privileges.
Other sources
A privilege escalation vulnerability was discovered in GitLab affecting versions 16.8 prior to 16.8.4 and 16.9 prior to 16.9.2. It was possible for a user with custom role of managegroupaccesstokens to rotate group access tokens with owner privileges. 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-1299.
— GitLab
Affected Software
Remediation
Information
Event History
Frequently Asked Questions
What is the severity of CVE-2024-1299?
CVE-2024-1299 is classified as a privilege escalation vulnerability.
How do I fix CVE-2024-1299?
To fix CVE-2024-1299, upgrade GitLab to version 16.8.4 or 16.9.2 or later.
Which versions of GitLab are affected by CVE-2024-1299?
CVE-2024-1299 affects GitLab versions 16.8 prior to 16.8.4 and 16.9 prior to 16.9.2.
What can a user with the `manage_group_access_tokens` role do in relation to CVE-2024-1299?
A user with the `manage_group_access_tokens` role could rotate group access tokens with owner privileges, leading to potential unauthorized access.
Is there a workaround for CVE-2024-1299 if I cannot upgrade immediately?
Currently, there is no documented workaround for CVE-2024-1299, so upgrading is essential to mitigate the vulnerability.