What is the severity of CVE-2020-11506?

CVE-2020-11506 has been classified as a high severity vulnerability due to its potential for file disclosure and exposure of sensitive information.

How do I fix CVE-2020-11506?

To fix CVE-2020-11506, upgrade GitLab to version 12.9.3 or later for both community and enterprise editions.

What versions of GitLab are affected by CVE-2020-11506?

CVE-2020-11506 affects GitLab versions from 10.7.0 through 12.9.2.

What type of vulnerability is CVE-2020-11506?

CVE-2020-11506 is a Workhorse bypass vulnerability that can lead to job artifact uploads and file disclosure.

What impact does CVE-2020-11506 have on GitLab users?

CVE-2020-11506 can result in unauthorized access to sensitive files and information through request smuggling attacks.

Vulnerability/
CVE-2020-11506

high

7.5

CWE

444

22/4/2020

4/8/2024

CVE-2020-11506

First published: Wed Apr 22 2020(Updated: )

An issue was discovered in GitLab 10.7.0 and later through 12.9.2. A Workhorse bypass could lead to job artifact uploads and file disclosure (Exposure of Sensitive Information) via request smuggling.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=10.7.0<12.7.9
GitLab	>=10.7.9<12.7.9
GitLab	>=12.8.0<12.8.9
GitLab	>=12.8.0<12.8.9
GitLab	>=12.9.0<12.9.3
GitLab	>=12.9.0<12.9.3

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-11506?
CVE-2020-11506 has been classified as a high severity vulnerability due to its potential for file disclosure and exposure of sensitive information.
How do I fix CVE-2020-11506?
To fix CVE-2020-11506, upgrade GitLab to version 12.9.3 or later for both community and enterprise editions.
What versions of GitLab are affected by CVE-2020-11506?
CVE-2020-11506 affects GitLab versions from 10.7.0 through 12.9.2.
What type of vulnerability is CVE-2020-11506?
CVE-2020-11506 is a Workhorse bypass vulnerability that can lead to job artifact uploads and file disclosure.
What impact does CVE-2020-11506 have on GitLab users?
CVE-2020-11506 can result in unauthorized access to sensitive files and information through request smuggling attacks.

agent/references
agent/type
agent/weakness
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/10.7.0
version/gitlab/10.7.9
version/gitlab/12.8.0
version/gitlab/12.9.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2020-11506?
CVE-2020-11506 has been classified as a high severity vulnerability due to its potential for file disclosure and exposure of sensitive information.
How do I fix CVE-2020-11506?
To fix CVE-2020-11506, upgrade GitLab to version 12.9.3 or later for both community and enterprise editions.
What versions of GitLab are affected by CVE-2020-11506?
CVE-2020-11506 affects GitLab versions from 10.7.0 through 12.9.2.
What type of vulnerability is CVE-2020-11506?
CVE-2020-11506 is a Workhorse bypass vulnerability that can lead to job artifact uploads and file disclosure.
What impact does CVE-2020-11506 have on GitLab users?
CVE-2020-11506 can result in unauthorized access to sensitive files and information through request smuggling attacks.