CVE-2020-6833
First published: Wed Feb 05 2020(Updated: )
An issue was discovered in GitLab EE 11.3 and later. A GitLab Workhorse bypass could lead to package and file disclosure via request smuggling.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=11.3.0<12.5.9 | |
| GitLab | >=12.6.0<12.6.6 | |
| GitLab | >=12.7.2<12.7.4 |
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-6833?
CVE-2020-6833 has been classified as a medium severity vulnerability due to its potential for package and file disclosure.
How do I fix CVE-2020-6833?
To remediate CVE-2020-6833, upgrade GitLab to version 12.7.4 or later or apply the recommended security patches.
What versions of GitLab are affected by CVE-2020-6833?
CVE-2020-6833 affects GitLab EE versions starting from 11.3.0 to 12.7.4, excluding 12.7.4.
What is the impact of CVE-2020-6833?
CVE-2020-6833 can allow attackers to bypass GitLab Workhorse and potentially disclose sensitive packages and files.
Is CVE-2020-6833 specific to GitLab EE?
Yes, CVE-2020-6833 specifically impacts GitLab Enterprise Edition.
- agent/type
- agent/references
- agent/author
- agent/severity
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- 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.3.0
- version/gitlab/12.6.0
- version/gitlab/12.7.2