GitLabApplication
CVE-2020-12277
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 10.8 through 12.9 has a vulnerability that allows someone to mirror a repository even if the feature is not activated.
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 confidenceBroken access control in GitLab versions 10.8-12.9 allows authenticated users to enable repository mirroring even when the feature has been disabled by administrators. This bypasses intended access controls configured at the instance or project level.
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
>= 10.8.0, < 12.7.8>= 12.8.0, < 12.8.8>= 12.9.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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Determine installed GitLab versionRun `sudo gitlab-rake gitlab:env:info` or check the GitLab admin area under /help for the version number. On the server, you can also check `/opt/gitlab/version` or use `gitlab-ctl version`.Affected if The installed version matches any of these ranges: 10.8.0 to 12.7.7, 12.8.0 to 12.8.7, or 12.9.0 to 12.9.0.
-
Identify if repository mirroring is disabledAs an administrator, go to the GitLab admin panel, navigate to Settings > Repository > Repository mirroring, or check the project-level settings under Project > Settings > Repository > Mirroring to see if the feature is explicitly disabled.Affected if Repository mirroring is disabled at the instance or project level, and the GitLab version is within the affected ranges listed above.
-
Test whether authenticated users can bypass the restrictionUsing a non-administrator authenticated user account, attempt to navigate to a project's Settings > Repository > Mirroring and try to add a mirror. If the option appears and allows submission when mirroring should be disabled, the vulnerability is present.Affected if An authenticated non-admin user can enable repository mirroring despite it being disabled by the administrator.
You are affected if your GitLab version falls within 10.8.0-12.7.7, 12.8.0-12.8.7, or 12.9.0-12.9.0 AND repository mirroring is configured to be disabled but users can still enable it.
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 data12.7.812.8.812.9.1
Upgrade GitLab to version 12.9.1 or later to receive the security patch. After upgrading, verify that repository mirroring controls function as expected per administrative settings.
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-12277 — 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-12277 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