dbcve.org
GitLabApplication

CVE-2024-6678

HIGH · 8.8 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 →
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 was discovered in GitLab CE/EE affecting all versions starting from 8.14 prior to 17.1.7, starting from 17.2 prior to 17.2.5, and starting from 17.3 prior to 17.3.2, which allows an attacker to trigger a pipeline as an arbitrary user under certain circumstances.

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 CE/EE contains an authorization bypass vulnerability where an unauthenticated or authenticated attacker can trigger CI/CD pipelines as arbitrary users due to insufficient validation of pipeline trigger requests. This enables privilege escalation within the GitLab instance.

MitigationUpgrade GitLab to version 17.1.7, 17.2.5, 17.3.2 or later to patch the authorization flaw. If immediate upgrade is not possible, review pipeline trigger tokens and restrict pipeline trigger API access.

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.14.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
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. Check installed GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check the GitLab admin panel under Help > Version to determine the exact version running.
    Affected if The installed version falls within 8.14.0 to 17.1.6, 17.2.0 to 17.2.4, or 17.3.0 to 17.3.1.
  2. Verify CI/CD pipeline triggers are accessible
    Check if the pipeline trigger API endpoint (typically /api/v4/projects/:id/trigger/pipeline) is accessible without authentication or with low-privilege user accounts.
    Affected if Pipeline trigger endpoints respond to unauthenticated requests or requests from non-maintainer users.
  3. Inspect pipeline trigger token configuration
    Review existing pipeline trigger tokens in the GitLab admin panel under CI/CD > Pipeline triggers, or query the API endpoint `/api/v4/projects/:id/triggers` with admin credentials.
    Affected if Multiple pipeline trigger tokens exist, especially tokens created unexpectedly or linked to users who should not have pipeline trigger privileges.
  4. Audit recent pipeline executions for anomalies
    Review pipeline logs in the CI/CD > Pipelines section of projects, or query the API `/api/v4/projects/:id/pipelines` to identify pipelines triggered by users with insufficient permissions.
    Affected if Pipelines were triggered by users who lack maintainer or developer access to the project, or pipelines show execution as different users than the trigger initiator.

You are affected if your GitLab version is within the affected ranges AND CI/CD pipeline triggers are exposed or show unauthorized execution activity.

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 to version 17.1.7, 17.2.5, 17.3.2 or later to patch the authorization flaw. If immediate upgrade is not possible, review pipeline trigger tokens and restrict pipeline trigger API access.

Recommended fix High confidence

17.1.7, 17.2.5, or 17.3.2 (choose the appropriate version based on your current branch)

  1. Determine your current GitLab version by running `gitlab-rake gitlab:env:info`
  2. Backup your GitLab instance using `gitlab-backup-create` or the omnibus backup tool
  3. Update your package repository: For Debian/Ubuntu run `apt-get update`; For RHEL/CentOS run `yum check-update`
  4. Stop GitLab services: `gitlab-ctl stop`
  5. Upgrade GitLab package: For Debian/Ubuntu run `apt-get install gitlab-ee=<version>` or `apt-get install gitlab-ce=<version>`; For RHEL/CentOS run `yum install gitlab-ee-<version>` or `yum install gitlab-ce-<version>`, replacing <version> with your target version (17.1.7, 17.2.5, or 17.3.2)
  6. Reconfigure GitLab: `gitlab-ctl reconfigure`
  7. Restart GitLab services: `gitlab-ctl restart`
  8. Verify the upgrade: Run `gitlab-rake gitlab:env:info` and confirm the version matches your target
Caveat Point releases typically contain no breaking changes; review GitLab release notes for any deprecation notices

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

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,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 $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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