GitLabApplication
CVE-2019-6787
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 Incorrect Access Control issue was discovered in GitLab Community and Enterprise Edition before 11.5.8, 11.6.x before 11.6.6, and 11.7.x before 11.7.1. The GitLab API allowed project Maintainers and Owners to view the trigger tokens of other project users.
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 confidenceThe GitLab API had an incorrect access control flaw that allowed project Maintainers and Owners to view trigger tokens belonging to other project users. Trigger tokens are sensitive CI/CD credentials that should only be accessible to their owners. This is a privilege escalation/information disclosure vulnerability where users with elevated but not administrative privileges could access sensitive authentication tokens beyond their authorized scope.
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
>= 8.12.0, < 11.5.8>= 11.6.0, < 11.6.6>= 11.7.0, < 11.7.1CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Determine your GitLab versionRun `sudo gitlab-rake gitlab:env:info` or check the GitLab admin dashboard under /admin/status. Look for the exact version number (e.g., 11.5.0, 11.6.5).Affected if The installed version is 8.12.0 or later but earlier than 11.5.8, OR 11.6.0-11.6.5, OR 11.7.0 (the specific 11.7.0 version before 11.7.1)
-
Identify if any projects use CI triggersNavigate to each project Settings CI/CD and expand the Triggers section, or query the API endpoint `/projects/:id/triggers` to list trigger tokens configured in your projects.Affected if You have projects with trigger tokens configured and the GitLab version is in the affected range
-
Verify access control on trigger tokensAs a user with Maintainer or Owner role on a project (not admin), query the GitLab API: `GET /projects/:id/triggers` without being the token owner. Check if the response includes trigger tokens belonging to other users.Affected if The API returns trigger tokens that you did not create, exposing tokens owned by other project members
You are affected if your GitLab version falls within 8.12.0 to 11.5.7, 11.6.0 to 11.6.5, or exactly 11.7.0 AND you have CI/CD triggers configured in any project where users share Maintainer or Owner roles.
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.
From vendor data11.5.811.6.611.7.1
Upgrade GitLab to version 11.5.8, 11.6.6, or 11.7.1 or later, which contains the access control fix for the API endpoint that exposes trigger tokens to unauthorized project members.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6787 — 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-2019-6787 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