dbcve.org
GitLabApplication

CVE-2024-8631

HIGH · 7.2 CVSS v3.1 Published 2024-09-12
Fix available
A fix is available. Upgrade to 17.1.7 / 17.2.5 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A privilege escalation issue has been discovered in GitLab EE affecting all versions starting from 16.6 prior to 17.1.7, from 17.2 prior to 17.2.5, and from 17.3 prior to 17.3.2. A user assigned the Admin Group Member custom role could have escalated their privileges to include other custom roles.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

GitLab EE versions prior to 17.1.7, 17.2.5, and 17.3.2 contain a privilege escalation vulnerability where users assigned the Admin Group Member custom role can escalate their privileges to include other custom roles they should not have access to.

MitigationUpgrade GitLab EE to version 17.1.7, 17.2.5, or 17.3.2 or later to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GitLabApplication
Affected:>= 16.6.0, < 17.1.7>= 17.2.0, < 17.2.5>= 17.3.0, < 17.3.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed GitLab EE version
    Run `sudo gitlab-rake gitlab:version` or check the GitLab admin area under Help > Version. Alternatively, check the /opt/gitlab/version.json file.
    Affected if Version is 16.6.0 through 17.1.6, 17.2.0 through 17.2.4, or 17.3.0 through 17.3.1 (i.e., any version prior to 17.1.7, 17.2.5, or 17.3.2)
  2. Verify custom roles feature is in use
    In GitLab admin area, navigate to Groups > [Select Group] > Settings > Roles and Permissions, or query the database table `custom_roles` if direct database access is available.
    Affected if Custom roles are defined or the custom_roles feature flag is enabled in the GitLab instance
  3. Identify users with Admin Group Member role
    In GitLab admin area, go to Admin Area > Users, filter by role or check Group > [Select Group] > Members to see assigned custom roles. Alternatively, query the database table `group_member_roles` for entries where role_id corresponds to the Admin Group Member custom role.
    Affected if Any users are assigned the Admin Group Member custom role within any group on the instance
  4. Check for unauthorized role assignments
    Review the group_member_roles table or Group > Members page for any instances where users with Admin Group Member role have been granted access to additional custom roles beyond what they should have.
    Affected if Users assigned Admin Group Member role have access to custom roles they should not normally have permission to manage

An organization is affected if they run a vulnerable GitLab EE version (prior to 17.1.7, 17.2.5, or 17.3.2) AND have custom roles enabled with the Admin Group Member role assigned to users who may have gained access to unauthorized roles.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 17.1.7 / 17.2.5 / 17.3.2 or later
Fixed in 17.1.717.2.517.3.2
Interim mitigation

Upgrade GitLab EE to version 17.1.7, 17.2.5, or 17.3.2 or later to remediate this vulnerability.

Recommended fix High confidence

17.1.7 (for 16.6-17.0), 17.2.5 (for 17.2.x), or 17.3.2 (for 17.3.x)

  1. 1. Identify the currently installed GitLab version by running `gitlab-rake gitlab:env:info` or checking the GitLab admin dashboard.
  2. 2. Based on the current version, determine the appropriate upgrade path: if running 16.6.x through 17.0.x, upgrade to 17.1.7 or later in the 17.1.x series; if running 17.2.x, upgrade to 17.2.5 or later in the 17.2.x series; if running 17.3.0 or 17.3.1, upgrade to 17.3.2 or later in the 17.3.x series.
  3. 3. Before upgrading, back up the GitLab database and repositories using `gitlab-backup-create` or the omnibus backup tool.
  4. 4. Follow the official GitLab upgrade documentation for your deployment method (Omnibus or source) to perform the upgrade.
  5. 5. After upgrade, verify the GitLab instance is operational and test that custom role assignments work as expected.
  6. 6. Review user accounts with Admin Group Member custom roles to ensure no unauthorized privilege escalation occurred.
Caveat Major version upgrades (e.g., 16.x to 17.x) may include breaking changes; review the GitLab release notes for migration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8631 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-8631 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data