GitLabApplication
CVE-2020-13298
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 · uneditedA vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. Conan package upload functionality was not properly validating the supplied parameters, which resulted in the limited files disclosure.
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's Conan package manager integration contains a parameter validation flaw in the package upload functionality. By supplying specially crafted parameters during Conan package upload, an attacker could access files outside the intended package scope, resulting in limited file disclosure.
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
< 13.1.10>= 13.2.0, < 13.2.8>= 13.3.0, < 13.3.4CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify GitLab installationCheck for GitLab installation by looking for /opt/gitlab directory, running `gitlab-rake gitlab:env:info`, or checking if gitlab-ctl command is availableAffected if GitLab is not installed - not affected by this CVE
-
Determine installed GitLab versionRun `gitlab-rake gitlab:git:version` or check /opt/gitlab/VERSION file, or use the GitLab admin interface at /admin/aboutAffected if Version is 13.1.x before 13.1.10, OR 13.2.x before 13.2.8, OR 13.3.x before 13.3.4 - potentially affected
-
Check if Conan package registry is enabledNavigate to GitLab admin area, go to Package Settings (or check /admin/application_settings/packages), or verify via API: GET /api/v4/application/settings look for `package_registry_enabled`Affected if Package registry is disabled - likely not affected (but version check still recommended)
-
Verify Conan package upload access controlsCheck project/group package settings or API endpoint GET /projects/:id/packages/conan/settings to see if unauthenticated or untrusted users can upload Conan packagesAffected if Untrusted or unauthenticated users have Conan upload permissions - at higher risk if version is affected
A user is affected if their GitLab version falls in any of the vulnerable ranges (pre-13.1.10, 13.2.0-13.2.7, or 13.3.0-13.3.3) AND the Conan package registry is enabled AND untrusted users can access Conan upload functionality.
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 data13.1.1013.2.813.3.4
Upgrade GitLab to version 13.1.10, 13.2.8, 13.3.4 or later. If upgrading is not immediately possible, restrict Conan package upload functionality to trusted users only.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-13298 — 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-13298 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