GitLabApplication
CVE-2020-10080
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 · uneditedGitLab 8.3 through 12.8.1 allows Information Disclosure. It was possible for certain non-members to access the Contribution Analytics page of a private group.
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 confidenceGitLab versions 8.3 through 12.8.1 had an improper access control vulnerability where non-members could access the Contribution Analytics page of private groups, exposing sensitive collaboration and contribution data to unauthorized users.
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.3.0, <= 12.8.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Identify installed GitLab versionAccess the GitLab administration area or run `gitlab-rake gitlab:env:info` to retrieve the exact version number installed in your environmentAffected if The version falls within >= 8.3.0 and <= 12.8.1, meaning the vulnerability is present in your version
-
Verify existence of private groupsNavigate to GitLab admin panel or use the API to list all groups in the instance and identify those set to private visibilityAffected if Private groups exist and the GitLab version is in the affected range
-
Confirm Contribution Analytics is enabledCheck if any private groups have the Contribution Analytics feature accessible. This can be verified by accessing the group dashboard and looking for the Analytics tab, or checking group settings for enabled featuresAffected if Private groups have Contribution Analytics enabled and your version is affected
-
Test unauthorized access to Contribution AnalyticsCreate a test user account that is NOT a member of a private group, then attempt to navigate directly to the Contribution Analytics page using the URL pattern: /groups/<group-name>/-/analytics/contributions. The request should be denied for a properly secured instanceAffected if Non-member users can view the Contribution Analytics page of private groups, confirming the authorization bypass exists
You are affected if your GitLab version is between 8.3.0 and 12.8.1 AND you have private groups with Contribution Analytics enabled, especially if non-member users can access that data.
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 to version 12.8.2 or later to patch the authorization bypass. Alternatively, if immediate upgrade is not possible, restrict access to the Contribution Analytics feature until the patch can be applied.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10080 — 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-10080 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