CVE-2020-6833

Description

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.

7.5

CVSS

Severity: High

CVSS 3.1 •

CVSS 2.0 •

EPSS 0.08%

Vendor Advisory gitlab.com Vendor Advisory gitlab.com

Affected: n/a n/a

References

Link	Tags
https://about.gitlab.com/blog/categories/releases/	release notes vendor advisory
https://about.gitlab.com/releases/2020/01/30/security-release-gitlab-12-7-4-released/	release notes vendor advisory

Frequently Asked Questions

What is the severity of CVE-2020-6833?: CVE-2020-6833 has been scored as a high severity vulnerability.
How to fix CVE-2020-6833?: To fix CVE-2020-6833, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2020-6833 being actively exploited in the wild?: As for now, there are no information to confirm that CVE-2020-6833 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.

This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.