CVE-2024-1250: Privilege Chaining in GitLab
First published: Mon Feb 12 2024(Updated: )
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 manage_group_access_tokens permission, they may be able to create group access tokens with Owner privileges, which may lead to privilege escalation.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=16.8.0<16.8.2 |
Remedy
Upgrade to versions 16.8.2 or above.
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
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.
- agent/severity
- agent/author
- agent/references
- agent/remedy
- agent/description
- agent/first-publish-date
- agent/type
- agent/event
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/title
- agent/weakness
- agent/last-modified-date
- agent/source
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/gitlab
- canonical/gitlab
- version/gitlab/16.8.0