dbcve.org
GitLabApplication

CVE-2020-10954

HIGH · 7.5 CVSS v3.1 Published 2020-03-27
Fix available
A fix is available. Upgrade to after 12.9 or later.
See remediation →
84/100
Remediation priority · High
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 through 12.9 is affected by a potential DoS in repository archive download.

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 through 12.9 contain a denial-of-service vulnerability in the repository archive download functionality. The vulnerability allows attackers to potentially crash or make the archive download feature unavailable, likely through resource exhaustion or malformed input processing.

MitigationUpgrade GitLab to version 12.9.1 or later (or the latest stable version). If immediate patching is not possible, consider rate-limiting archive download endpoints and monitoring for anomalous download patterns.

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.9

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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 the installed GitLab version
    Access the GitLab administration interface or use the GitLab API endpoint /api/v4/version to retrieve the running version number
    Affected if The displayed version is 12.9 or any earlier version (e.g., 12.8, 12.7, etc.)
  2. Confirm the version is within the affected range
    Compare the retrieved version against the affected range: any version from 12.0 through 12.9 inclusive is vulnerable
    Affected if The version number is 12.9 or lower
  3. Determine if repository archive download is accessible
    Verify that repository archive download functionality is enabled and accessible to users on the instance (this feature is typically enabled by default for repositories)
    Affected if Archive download is available and the GitLab version is 12.9 or lower

The environment is affected if GitLab version 12.9 or earlier is installed and the repository archive download feature is accessible to users.

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 a release after 12.9
Interim mitigation

Upgrade GitLab to version 12.9.1 or later (or the latest stable version). If immediate patching is not possible, consider rate-limiting archive download endpoints and monitoring for anomalous download patterns.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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