GitLabApplication
CVE-2024-5655
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 15.8 prior to 16.11.5, starting from 17.0 prior to 17.0.3, and starting from 17.1 prior to 17.1.1, 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 confidenceA broken access control vulnerability in GitLab CI/CD pipeline triggering mechanism allows authenticated attackers to trigger pipelines in the name of other users. This is an authorization bypass where the pipeline execution does not properly validate the requesting user's identity against the pipeline's owner.
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
>= 15.8.0, < 16.11.5>= 17.0.0, < 17.0.3= 17.1.0CVSS 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 GitLab versionRun `sudo gitlab-rake gitlab:env:info` or access the GitLab admin dashboard and navigate to the version information section. Note the exact version number (for example, 16.11.4 or 17.1.0).Affected if Version is 15.8.0 or higher but below 16.11.5; OR version 17.0.0 through 17.0.3; OR exactly version 17.1.0
-
Confirm CI/CD pipeline feature is activeCheck if any projects in the GitLab instance have .gitlab-ci.yml files or have ever run CI/CD pipelines. Look at the Projects page and search for repositories with CI/CD configuration, or query the database table `ci_pipelines` if direct database access is available.Affected if Any project has CI/CD pipelines configured or has executed pipelines in the past
-
Identify pipeline triggering configurationNavigate to Project Settings > CI/CD > General pipelines (or /settings/ci_cd) for projects using pipelines. Review whether pipeline triggers are enabled and which users or roles have permission to run pipelines manually.Affected if Users with authenticated access (beyond pipeline owner) can manually trigger pipelines
You are affected if your GitLab version falls within the vulnerable ranges AND CI/CD pipelines exist that can be manually triggered by authenticated users other than the pipeline owner.
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 · scoped16.11.517.0.3
Upgrade GitLab to version 16.11.5, 17.0.3, or 17.1.1 (or later) to patch the authorization flaw in pipeline triggering.
Upgrade to GitLab 16.11.5+, 17.0.3+, or 17.1.1+ (preferably latest stable 16.11.x or 17.x)
- 1. Backup your GitLab instance data and configuration before proceeding with the upgrade
- 2. Schedule a maintenance window for the upgrade process
- 3. For GitLab 16.x installations: upgrade to version 16.11.5 or later (recommended: latest 16.11.x stable)
- 4. For GitLab 17.0.x installations: upgrade to version 17.0.3 or later (recommended: latest 17.0.x stable)
- 5. For GitLab 17.1.x installations: upgrade to version 17.1.1 or later (recommended: latest 17.1.x stable or 17.2+)
- 6. After upgrade, verify the GitLab instance is operational and test that pipeline execution works correctly
- 7. Review audit logs to confirm no unauthorized pipeline triggers occurred during the vulnerable period
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5655 — 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-5655 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