dbcve.org
GitLabApplication

CVE-2020-10083

CRITICAL · 9.1 CVSS v3.1 Published 2020-03-13
Fix available
A fix is available. Upgrade to after 12.8.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
GitLab 12.7 through 12.8.1 has Insecure Permissions. Under certain conditions involving groups, project authorization changes were not being applied.

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 confidence

GitLab versions 12.7 through 12.8.1 contain an insecure permissions vulnerability where project authorization changes involving groups were not being properly applied. This authorization bypass could allow users to retain access to projects they should no longer have permission to view or modify.

MitigationUpgrade GitLab to version 12.8.2 or later to remediate the authorization bypass. After upgrading, audit existing group-project membership to ensure permissions are correctly enforced.

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
Affected:>= 12.7.0, <= 12.8.1

CVSS 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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed GitLab version
    Run `gitlab-rake gitlab:env:info` or check the GitLab admin panel under Help > Version to obtain the exact version number
    Affected if Version is 12.7.0, 12.7.x, 12.8.0, or 12.8.1 (any version from 12.7.0 through 12.8.1 inclusive)
  2. Identify projects with group authorizations
    Query the database or use the GitLab admin panel to list all projects that have group access permissions configured (check the project settings under Repository > Members > Groups, or query the `project_group_links` table)
    Affected if Any project has group-based access shares configured and the GitLab instance was running version 12.7-12.8.1 when those group links were created or modified
  3. Review recent group authorization changes
    Check GitLab audit logs (Admin Area > Monitoring > Audit Events) for events involving project authorization changes to groups, focusing on the time period when the instance ran versions 12.7.x through 12.8.1
    Affected if Group authorization entries were added, modified, or removed while GitLab was on an affected version
  4. Compare current group memberships against expected permissions
    Export current project-group associations and compare against documented or expected access policies to identify any discrepancies where users from groups retain access they should no longer have
    Affected if Users from groups appear to have access to projects where their group authorization should have been removed or modified

The environment is affected if GitLab is version 12.7.0 through 12.8.1 and there are projects with group authorizations that may have been modified during that time, as the authorization bypass could allow unintended retained access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 12.8.1
Interim mitigation

Upgrade GitLab to version 12.8.2 or later to remediate the authorization bypass. After upgrading, audit existing group-project membership to ensure permissions are correctly enforced.

Recommended fix Moderate confidence

GitLab 12.8.2 or later (recommended: latest stable 12.x release)

  1. 1. Back up your GitLab instance data and configuration
  2. 2. Plan your upgrade path according to GitLab's official upgrade documentation
  3. 3. Upgrade GitLab from version 12.7.x or 12.8.x to version 12.8.2 or later (preferably the latest 12.x stable release)
  4. 4. After upgrade, verify that group and project authorization changes are properly applied
  5. 5. Test the permission changes by modifying group memberships and project authorizations to confirm the fix is effective
Caveat Upgrading across minor versions may require reading GitLab's upgrade guides for potential configuration changes; also note that GitLab 12.x has reached end-of-life and further upgrades to newer major versions may be needed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-10083 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-10083 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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