dbcve.org
GitLabApplication

CVE-2020-10955

MEDIUM · 6.5 CVSS v3.1 Published 2020-03-27
Fix available
A fix is available. Upgrade to 12.9.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 EE/CE 11.1 through 12.9 is vulnerable to parameter tampering on an upload feature that allows an unauthorized user to read content available under specific folders.

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 confidence

GitLab EE/CE versions 11.1 through 12.9 contain an Insecure Direct Object Reference (IDOR) vulnerability in the upload feature. Through parameter tampering, an unauthenticated or unauthorized user can manipulate upload parameters to access and read content stored in specific folders they should not have access to.

MitigationUpgrade GitLab to version 12.9.1 or later to patch the vulnerable upload feature. Verify that unauthorized users can no longer access restricted folders after upgrading.

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:>= 11.1.0, < 12.9.1
Debian LinuxOperating system
Affected:= 10.0

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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

  1. Identify installed GitLab version
    Run command: gitlab-rake gitlab:env:info or check /opt/gitlab/version or look at the GitLab admin panel under 'Help' > 'Version'
    Affected if Version is 11.1.0 through 12.9.0 (inclusive)
  2. Confirm version is within vulnerable range
    Compare your installed version number against the affected range: >= 11.1.0 and < 12.9.1
    Affected if Installed version starts with 11.1, 11.2, 11.3, 11.4, 11.5, 11.6, 11.7, 11.8, 11.9, 11.10, 11.11, 12.0, 12.1, 12.2, 12.3, 12.4, 12.5, 12.6, 12.7, 12.8, or 12.9.0
  3. Verify upload feature configuration
    Check if the file upload functionality is enabled in GitLab settings. Review project/group settings related to uploads and attachments.
    Affected if Upload feature is enabled and accessible to users (this is typically enabled by default)

You are affected if your GitLab version is 11.1.0 through 12.9.0 and the upload feature is enabled, allowing potential unauthorized access to restricted upload folders via parameter tampering.

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.

From vendor data
Upgrade available Upgrade to 12.9.1 or later
Fixed in 12.9.1
Interim mitigation

Upgrade GitLab to version 12.9.1 or later to patch the vulnerable upload feature. Verify that unauthorized users can no longer access restricted folders after upgrading.

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-10955 — 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-10955 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