dbcve.org
GitLabApplication

CVE-2024-8114

HIGH · 8.8 CVSS v3.1 Published 2024-11-26
Fix available
A fix is available. Upgrade to 17.4.5 / 17.5.3 or later.
See remediation →
94/100
Remediation priority · Urgent
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
An issue has been discovered in GitLab CE/EE affecting all versions from 8.12 before 17.4.5, 17.5 before 17.5.3, and 17.6 before 17.6.1. This issue allows an attacker with access to a victim's Personal Access Token (PAT) to escalate privileges.

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 · moderate confidence

This GitLab vulnerability allows an attacker who obtains a victim's Personal Access Token (PAT) to perform privilege escalation, potentially gaining higher-level permissions than the token originally possessed. The specific technical mechanism (injection, validation bypass, etc.) is not detailed in the available advisory.

MitigationUpgrade GitLab to version 17.4.5, 17.5.3, 17.6.1 or later. Additionally, revoke potentially compromised PATs and review token permissions and audit logs for suspicious activity.

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:>= 8.12.0, < 17.4.5>= 17.5.0, < 17.5.3= 17.6.0

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 your installed GitLab version
    Run 'sudo gitlab-rake gitlab:env:info' or check the GitLab admin interface under Admin Area > Monitoring > Version. Alternatively, check the version file at /opt/gitlab/version or the GitLab package version.
    Affected if The installed version is >= 8.12.0 AND < 17.4.5, OR >= 17.5.0 AND < 17.5.3, OR = 17.6.0
  2. Identify active Personal Access Tokens
    In GitLab admin interface, go to Admin Area > Tokens to review active PATs. Use the API endpoint /api/v4/personal_access_tokens with admin credentials to list all tokens.
    Affected if Any Personal Access Tokens exist in the system - the vulnerability exploits compromised PATs to perform privilege escalation
  3. Review audit logs for permission escalation events
    Navigate to Admin Area > Audit Logs and filter for event types related to token usage and permission changes. Look for events where user permissions changed unexpectedly or tokens were used in ways inconsistent with their assigned scope.
    Affected if Audit logs show unexpected permission changes or token activity that does not align with the token's original scope or user role
  4. Check for unauthorized role or access level changes
    In GitLab admin interface, review Admin Area > Users and examine user access levels. Look for users who have gained admin, maintainer, or owner roles they should not possess, or check audit events for role_assignment events.
    Affected if Users have been granted higher privileges than their normal role should permit, suggesting potential exploitation

Your environment is affected if GitLab version is in the vulnerable range (8.12.0 to 17.4.4, 17.5.0 to 17.5.2, or 17.6.0) AND Personal Access Tokens are in use, with any evidence of unauthorized permission escalation in audit logs.

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.4.5 / 17.5.3 or later
Fixed in 17.4.517.5.3
Interim mitigation

Upgrade GitLab to version 17.4.5, 17.5.3, 17.6.1 or later. Additionally, revoke potentially compromised PATs and review token permissions and audit logs for suspicious activity.

Recommended fix High confidence

Upgrade to 17.4.5, 17.5.3, 17.6.1 or later (preferably latest 17.x stable release)

  1. Identify your current GitLab version using the GitLab Rails console or the admin area /help page
  2. Determine which upgrade path applies based on your current version: for 8.12+ to <17.4.5 upgrade to 17.4.5+, for 17.5.x to <17.5.3 upgrade to 17.5.3+, for 17.6.0 upgrade to 17.6.1+
  3. Back up your GitLab database and repository storage before upgrading
  4. Upgrade GitLab to the appropriate fixed version (17.4.5, 17.5.3, 17.6.1, or latest 17.x stable)
  5. Verify the upgrade was successful by checking the version in Admin Area > Monitor > Version
  6. Review user Personal Access Tokens and revoke any suspicious or unknown tokens in Admin Area > User Settings > Access Tokens
  7. Ensure webhook and API integrations use tokens with minimal required scopes
Caveat Major version upgrades from 8.x/9.x to 17.x require careful migration planning; review GitLab upgrade docs for intermediate steps

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

Fix this in GitLab Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8114 — 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-8114 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