CVE-2020-13268: Infoleak
First published: Wed Jun 10 2020(Updated: )
A specially crafted request could be used to confirm the existence of files hosted on object storage services, without disclosing their contents. This vulnerability affects GitLab CE/EE 12.10 and later through 13.0.1
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=12.10.0<=13.0.1 | |
| GitLab | >=12.10.0<=13.0.1 |
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-13268?
CVE-2020-13268 is classified as a moderate severity vulnerability.
How does CVE-2020-13268 affect GitLab?
CVE-2020-13268 allows an attacker to confirm the existence of files hosted on GitLab's object storage without revealing their contents.
Which versions of GitLab are impacted by CVE-2020-13268?
CVE-2020-13268 affects GitLab CE/EE versions 12.10.0 through 13.0.1.
How can I remediate CVE-2020-13268?
To fix CVE-2020-13268, upgrade to GitLab version 13.0.2 or later.
What types of object storage does CVE-2020-13268 target?
CVE-2020-13268 targets object storage services used by GitLab for managing hosted files.
- agent/type
- agent/references
- agent/weakness
- 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/12.10.0
- version/gitlab/13.0.1