GitLabApplication
CVE-2024-8970
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 · uneditedAn issue was discovered in GitLab CE/EE affecting all versions starting from 11.6 prior to 17.2.9, starting from 17.3 prior to 17.3.5, and starting from 17.4 prior to 17.4.2, which allows an attacker to trigger a pipeline as another 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 · moderate confidenceAn authentication bypass in GitLab's pipeline trigger mechanism allows authenticated attackers to trigger pipelines under other users' contexts by exploiting improper user context handling during pipeline initialization.
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
>= 11.6.0, < 17.2.9>= 17.3.0, < 17.3.5>= 17.4.0, < 17.4.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed GitLab versionRun `sudo gitlab-rake gitlab:env:info` or check the GitLab Administration dashboard under Help > Version. Compare the version number against the affected ranges: < 17.2.9, 17.3.0-17.3.4, or 17.4.0-17.4.1Affected if The installed version falls within any of the affected ranges (11.6.0 to 17.2.8, 17.3.0 to 17.3.4, or 17.4.0 to 17.4.1)
-
Identify active pipeline triggersNavigate to Project Settings > CI/CD > Pipeline triggers, or use the GitLab API endpoint `/projects/:id/triggers` to list trigger tokens. Identify which projects have triggers configuredAffected if Pipeline triggers exist in any project within the GitLab instance
-
Review audit logs for pipeline trigger eventsAccess the Audit Log under Admin Area > Monitoring > Audit Events, or use the API endpoint `/audit_events`. Filter for event type `pipeline_trigger` and examine the `user` field against the `owner` or `triggering_user` to detect mismatchesAffected if Audit logs show pipeline trigger events where the triggering user differs from the user context the pipeline executed under
-
Examine recent pipeline executions for anomaliesReview recent pipeline runs in the CI/CD pipeline browser. Check the pipeline details for the Triggerer field and compare it to the user associated with the pipeline job execution. Look for pipelines triggered via API where the author does not match expected behaviorAffected if Recent pipelines show execution under a user context that does not match the triggerer's identity
You are affected if running a vulnerable GitLab version AND pipeline triggers are enabled and used in your environment, with evidence of unauthorized user context in audit logs or pipeline executions.
Generated from the published advisory. Verify against your own configuration.
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 · scoped17.2.917.3.517.4.2
Upgrade to GitLab 17.2.9, 17.3.5, or 17.4.2 or later per the version matrix. Review pipeline trigger configurations and audit recent pipeline executions for signs of unauthorized use.
17.2.9, 17.3.5, or 17.4.2 (or later stable release)
- Backup your GitLab instance data before proceeding with the upgrade
- Check your current GitLab version in the GitLab Admin Area under '/admin','Plan your upgrade path based on your current version - you may need to upgrade through intermediate versions to reach a fixed release
- Upgrade GitLab to one of the fixed versions: 17.2.9, 17.3.5, or 17.4.2 (or the latest stable release in your desired branch)
- After upgrade, verify the version in Admin Area to confirm the fix is applied
- Review pipeline trigger permissions to ensure only authorized users can trigger pipelines
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8970 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-8970 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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