What is the severity of CVE-2020-11505?

CVE-2020-11505 is considered a moderate severity vulnerability due to the potential exposure of sensitive information.

How do I fix CVE-2020-11505?

To fix CVE-2020-11505, upgrade GitLab to versions 12.7.9, 12.8.9, or 12.9.3 or higher.

What types of GitLab editions are affected by CVE-2020-11505?

Both GitLab Community Edition and Enterprise Edition are affected by CVE-2020-11505.

What is the main issue with CVE-2020-11505?

The main issue with CVE-2020-11505 is a Workhorse bypass that could lead to unauthorized NuGet package and file disclosures.

Which versions of GitLab are vulnerable to CVE-2020-11505?

GitLab versions before 12.7.9, 12.8.x before 12.8.9, and 12.9.x before 12.9.3 are vulnerable to CVE-2020-11505.

Vulnerability/
CVE-2020-11505

high

7.5

CWE

444

22/4/2020

4/8/2024

CVE-2020-11505

First published: Wed Apr 22 2020(Updated: )

An issue was discovered in GitLab Community Edition (CE) and Enterprise Edition (EE) before 12.7.9, 12.8.x before 12.8.9, and 12.9.x before 12.9.3. A Workhorse bypass could lead to NuGet package and file disclosure (Exposure of Sensitive Information) via request smuggling.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	<12.7.9
GitLab	<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-11505?
CVE-2020-11505 is considered a moderate severity vulnerability due to the potential exposure of sensitive information.
How do I fix CVE-2020-11505?
To fix CVE-2020-11505, upgrade GitLab to versions 12.7.9, 12.8.9, or 12.9.3 or higher.
What types of GitLab editions are affected by CVE-2020-11505?
Both GitLab Community Edition and Enterprise Edition are affected by CVE-2020-11505.
What is the main issue with CVE-2020-11505?
The main issue with CVE-2020-11505 is a Workhorse bypass that could lead to unauthorized NuGet package and file disclosures.
Which versions of GitLab are vulnerable to CVE-2020-11505?
GitLab versions before 12.7.9, 12.8.x before 12.8.9, and 12.9.x before 12.9.3 are vulnerable to CVE-2020-11505.

agent/references
agent/type
agent/author
agent/weakness
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/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-11505?
CVE-2020-11505 is considered a moderate severity vulnerability due to the potential exposure of sensitive information.
How do I fix CVE-2020-11505?
To fix CVE-2020-11505, upgrade GitLab to versions 12.7.9, 12.8.9, or 12.9.3 or higher.
What types of GitLab editions are affected by CVE-2020-11505?
Both GitLab Community Edition and Enterprise Edition are affected by CVE-2020-11505.
What is the main issue with CVE-2020-11505?
The main issue with CVE-2020-11505 is a Workhorse bypass that could lead to unauthorized NuGet package and file disclosures.
Which versions of GitLab are vulnerable to CVE-2020-11505?
GitLab versions before 12.7.9, 12.8.x before 12.8.9, and 12.9.x before 12.9.3 are vulnerable to CVE-2020-11505.