Security readout for executives and security teams
Plain-English summary
A GitLab Enterprise Edition permission bug could let a user with a specific custom role create group access tokens with Owner-level privileges. That could let an already-privileged insider or compromised account expand control over a group. Exposure appears limited to GitLab EE 16.8 before 16.8.2.
Executive priority
Treat as a targeted privilege escalation issue, not a broad unauthenticated emergency. Prioritize GitLab EE 16.8 environments using custom roles or sensitive groups, then verify token activity and upgrade status.
Technical view
CVE-2024-1250 affects GitLab EE versions starting at 16.8 and before 16.8.2. Users assigned a custom role containing manage_group_access_tokens may be able to create group access tokens with Owner privileges, causing privilege escalation. CVSS is 6.5 with network access, low complexity, high privileges required, and high confidentiality/integrity impact.
Likely exposure
Organizations running GitLab EE 16.8 before 16.8.2 are the relevant exposure set, especially groups using custom roles with manage_group_access_tokens. GitLab versions outside the stated affected range are not identified as affected in the provided sources.
Exploitation context
No provided source or KEV entry indicates active exploitation. Abuse requires an account already holding a custom role with manage_group_access_tokens, so the main concern is insider misuse or escalation from a compromised privileged account.
Researcher notes
The provided evidence defines the affected range and privilege condition, but does not include exploit details, observed exploitation, or full remediation notes beyond the fixed-version boundary. Focus validation on custom-role authorization behavior and token privilege outcomes without creating offensive procedures.
Mitigation direction
- Upgrade affected GitLab EE 16.8 deployments to 16.8.2 or later.
- Review GitLab vendor guidance for any additional hardening or backport details.
- Audit custom roles that include manage_group_access_tokens.
- Temporarily restrict group access token management to trusted administrators where feasible.
- Rotate suspicious group access tokens created during the exposure window.
Validation and detection
- Inventory GitLab EE version numbers across self-managed deployments.
- Identify groups using custom roles with manage_group_access_tokens.
- Review group access tokens for unexpected Owner-level privileges.
- Check audit logs for token creation by custom-role users.
- Confirm upgraded instances report 16.8.2 or later.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-268: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-1250 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N1.25.2GitLabVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitLab Issue #439175CVE reference, GitLab · issue-tracking
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Privilege Chaining
Privilege Chaining represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.