CVE-2020-13326
First published: Tue Sep 29 2020(Updated: )
A vulnerability was discovered in GitLab versions prior to 13.1. Under certain conditions the restriction for Github project import could be bypassed.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=11.8.0<12.10.13 | |
| GitLab | >=13.0.0<13.0.8 | |
| GitLab | >=13.1.0<13.1.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2020-13326?
CVE-2020-13326 has a high severity rating due to its potential to allow unauthorized access to private Github projects during import.
How do I fix CVE-2020-13326?
To fix CVE-2020-13326, you should upgrade to GitLab version 13.1.3 or later.
What versions of GitLab are affected by CVE-2020-13326?
CVE-2020-13326 affects GitLab versions prior to 13.1, including versions from 11.8.0 to 12.10.13 and 13.0.0 to 13.0.8.
What kind of vulnerability is CVE-2020-13326?
CVE-2020-13326 is a security vulnerability that allows the bypass of restrictions on Github project imports.
Is there a workaround for CVE-2020-13326?
There are no official workarounds for CVE-2020-13326; upgrading to the patched version is recommended.
- agent/references
- agent/type
- agent/author
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/gitlab
- canonical/gitlab
- version/gitlab/11.8.0
- version/gitlab/13.0.0
- version/gitlab/13.1.0