What is the severity of CVE-2019-13011?

CVE-2019-13011 is considered a medium severity vulnerability due to its potential for brute-force attacks on merge request template names.

How do I fix CVE-2019-13011?

To fix CVE-2019-13011, it is recommended to upgrade GitLab Enterprise Edition to version 12.0.3 or later.

What type of vulnerability is CVE-2019-13011?

CVE-2019-13011 is a vulnerability that allows unauthorized users to enumerate merge request template names through excessive algorithmic complexity.

Which versions of GitLab are affected by CVE-2019-13011?

CVE-2019-13011 affects GitLab Enterprise Edition versions from 8.11.0 to 12.0.2.

Who is at risk from CVE-2019-13011?

Users with access to a GitLab project, but not its repository, are at risk from CVE-2019-13011 due to potential information leakage.

Vulnerability/
CVE-2019-13011

medium

4.3

CWE

400

10/3/2020

4/8/2024

CVE-2019-13011

First published: Tue Mar 10 2020(Updated: )

An issue was discovered in GitLab Enterprise Edition 8.11.0 through 12.0.2. By using brute-force a user with access to a project, but not it's repository could create a list of merge requests template names. It has excessive algorithmic complexity.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=8.11.0<=12.0.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-13011?
CVE-2019-13011 is considered a medium severity vulnerability due to its potential for brute-force attacks on merge request template names.
How do I fix CVE-2019-13011?
To fix CVE-2019-13011, it is recommended to upgrade GitLab Enterprise Edition to version 12.0.3 or later.
What type of vulnerability is CVE-2019-13011?
CVE-2019-13011 is a vulnerability that allows unauthorized users to enumerate merge request template names through excessive algorithmic complexity.
Which versions of GitLab are affected by CVE-2019-13011?
CVE-2019-13011 affects GitLab Enterprise Edition versions from 8.11.0 to 12.0.2.
Who is at risk from CVE-2019-13011?
Users with access to a GitLab project, but not its repository, are at risk from CVE-2019-13011 due to potential information leakage.

agent/references
agent/type
agent/weakness
agent/author
agent/severity
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/8.11.0
version/gitlab/12.0.2

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-2019-13011?
CVE-2019-13011 is considered a medium severity vulnerability due to its potential for brute-force attacks on merge request template names.
How do I fix CVE-2019-13011?
To fix CVE-2019-13011, it is recommended to upgrade GitLab Enterprise Edition to version 12.0.3 or later.
What type of vulnerability is CVE-2019-13011?
CVE-2019-13011 is a vulnerability that allows unauthorized users to enumerate merge request template names through excessive algorithmic complexity.
Which versions of GitLab are affected by CVE-2019-13011?
CVE-2019-13011 affects GitLab Enterprise Edition versions from 8.11.0 to 12.0.2.
Who is at risk from CVE-2019-13011?
Users with access to a GitLab project, but not its repository, are at risk from CVE-2019-13011 due to potential information leakage.