GitLabApplication
CVE-2020-8795
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 · uneditedIn GitLab Enterprise Edition (EE) 12.5.0 through 12.7.5, sharing a group with a group could grant project access to unauthorized 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 confidenceIn GitLab Enterprise Edition versions 12.5.0 through 12.7.5, a flaw in the group sharing mechanism allowed users to gain unauthorized access to projects. When sharing a group with another group, the access control logic failed to properly enforce permission boundaries, potentially exposing sensitive project data to users who should not have 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
>= 12.5.0, <= 12.7.5CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check your GitLab Enterprise Edition versionLog into the GitLab admin area and navigate to the Admin Overview section, or run `gitlab-rake gitlab:env:info` on the server to display the installed version.Affected if The installed version falls within the range 12.5.0 to 12.7.5 inclusive.
-
Verify if group sharing is enabled in your instanceAs an administrator, go to Admin Area > Settings > General > Visibility and access controls, and check if the option 'Allow users to invite group members to projects' or similar group sharing options are enabled.Affected if Group sharing features are enabled in the GitLab instance.
-
Identify active group-to-group sharing configurationsReview group settings under each group's 'Share with group' page to see if any groups have been shared with other groups. Use the GitLab API (GET /groups/:id) or check the database table `group_group_links` if direct database access is available.Affected if Groups have been shared with other groups in your hierarchy.
-
Review audit logs for suspicious group sharing activityNavigate to Admin Area > Audit Events, or use the API endpoint /audit_events, and filter for event types related to group sharing. Look for unauthorized group link creations or unexpected access grants.Affected if Audit logs show group sharing events that were not initiated by authorized administrators or owners.
You are affected if your GitLab EE version is between 12.5.0 and 12.7.5 inclusive AND group-to-group sharing is or was in use, allowing potential unauthorized project access.
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 dataUpgrade GitLab EE to version 12.7.6 or later to patch the authorization bypass. Review audit logs to check for any unauthorized access that may have occurred while the vulnerable version was in use.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-8795 — 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-2020-8795 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