GitLabApplication
CVE-2020-10090
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 11.7 through 12.8.1 allows Information Disclosure. Under certain group conditions, group epic information was unintentionally being disclosed.
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 confidenceGitLab versions 11.7 through 12.8.1 contain an information disclosure vulnerability where group epic information was unintentionally disclosed under certain group conditions. The vulnerability allows unauthorized access to sensitive metadata about group epics that should have been restricted based on user permissions or group visibility settings.
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.7.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.
-
Check installed GitLab versionRun `gitlab-rake gitlab:env:info` or check the GitLab admin area > Admin area > Overview > Dashboard to see the current GitLab versionAffected if The displayed version is >= 11.7.0 and <= 12.8.1
-
Verify GitLab omnibus versionRun `cat /opt/gitlab/version` or `gitlab --version` from the GitLab server command lineAffected if The version output shows a release between 11.7.0 and 12.8.1 inclusive
-
Confirm epics feature is enabledNavigate to a group's Settings > General > Permissions and verify if the Epics feature is enabled for the group, or query the database: `SELECT name, epics_enabled FROM namespaces WHERE type = 'Group';`Affected if Epics are enabled on any group in the GitLab instance
-
Inspect group visibility settingsReview group visibility settings at Group > Settings > General > Visibility and check if any groups have public or internal visibility with epics enabledAffected if Groups with public or internal visibility have epics enabled, allowing potential unauthorized access to epic metadata
You are affected if your GitLab version falls within 11.7.0 to 12.8.1 AND you have groups with the epics feature enabled, particularly with non-restricted visibility settings.
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 information disclosure vulnerability. Verify group permission configurations after upgrading to ensure epic data is properly restricted.
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-2020-10090 — 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-10090 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