GitLabApplication
CVE-2020-10952
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 EE/CE 8.11 through 12.9.1 allows blocked users to pull/push docker images.
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 EE/CE versions 8.11 through 12.9.1 contains an authorization bypass where users who have been blocked in GitLab can still authenticate to the integrated Docker Registry and pull/push container images. The block status is not properly enforced on Docker registry operations.
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.11.0, <= 12.9.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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 versionRun `sudo gitlab-rake gitlab:env:info` or check the GitLab admin area under /admin/application_settings to find the installed version.Affected if The version falls within 8.11.0 through 12.9.1 (inclusive).
-
Verify Docker Registry is integratedCheck if the integrated Docker Registry is enabled. In GitLab, go to Admin Area > Settings > Registry or inspect the gitlab.rb configuration file for `registry['enable'] = true`.Affected if Docker Registry is enabled and integrated with this GitLab instance.
-
Identify blocked usersIn GitLab admin area, navigate to Users area and filter for 'Blocked' status, or run `sudo gitlab-rake gitlab:blocked_users` to list blocked accounts.Affected if There are blocked user accounts in the system who could potentially authenticate to the registry.
-
Confirm registry authentication is activeVerify that the registry requires GitLab authentication. Check if `registry['auth_token_expire_in']` is set in gitlab.rb, or attempt a Docker login to the registry endpoint (registry.gitlab.example.com) using a blocked user's credentials.Affected if Docker registry authentication is configured and a blocked user can successfully authenticate and perform pull/push operations.
You are affected if your GitLab version is between 8.11.0 and 12.9.1, the Docker Registry is enabled, and blocked users exist who could authenticate to the registry.
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.9.2 or later where this vulnerability is patched. Alternatively, if immediate upgrade is not feasible, consider restricting or disabling the Docker registry temporarily until the upgrade can be performed.
Fix this in GitLab
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10952 — 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-10952 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