What is the severity of CVE-2019-10113?

CVE-2019-10113 has a medium severity classification due to its potential for uncontrolled resource consumption.

How do I fix CVE-2019-10113?

To fix CVE-2019-10113, upgrade GitLab to version 11.7.9, 11.8.4, or 11.9.2 or later.

Which GitLab versions are affected by CVE-2019-10113?

CVE-2019-10113 affects GitLab Community and Enterprise Editions prior to 11.7.8, 11.8.x before 11.8.4, and 11.9.x before 11.9.2.

What kind of issue does CVE-2019-10113 represent?

CVE-2019-10113 represents an issue related to concurrent API requests causing uncontrolled resource consumption.

Is there a workaround for CVE-2019-10113?

There are no specific workarounds for CVE-2019-10113, so it is recommended to update to a patched version.

Vulnerability/
CVE-2019-10113

high

7.5

CWE

400

16/5/2019

4/8/2024

CVE-2019-10113

First published: Thu May 16 2019(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition before 11.7.8, 11.8.x before 11.8.4, and 11.9.x before 11.9.2. Making concurrent GET /api/v4/projects/<id>/languages requests may allow Uncontrolled Resource Consumption.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	<11.7.8
GitLab	<11.7.8
GitLab	>=11.8.0<11.8.4
GitLab	>=11.8.0<11.8.4
GitLab	>=11.9.0<11.9.2
GitLab	>=11.9.0<11.9.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-10113?
CVE-2019-10113 has a medium severity classification due to its potential for uncontrolled resource consumption.
How do I fix CVE-2019-10113?
To fix CVE-2019-10113, upgrade GitLab to version 11.7.9, 11.8.4, or 11.9.2 or later.
Which GitLab versions are affected by CVE-2019-10113?
CVE-2019-10113 affects GitLab Community and Enterprise Editions prior to 11.7.8, 11.8.x before 11.8.4, and 11.9.x before 11.9.2.
What kind of issue does CVE-2019-10113 represent?
CVE-2019-10113 represents an issue related to concurrent API requests causing uncontrolled resource consumption.
Is there a workaround for CVE-2019-10113?
There are no specific workarounds for CVE-2019-10113, so it is recommended to update to a patched version.

agent/type
agent/references
agent/severity
agent/weakness
agent/author
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.8.0
version/gitlab/11.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-2019-10113?
CVE-2019-10113 has a medium severity classification due to its potential for uncontrolled resource consumption.
How do I fix CVE-2019-10113?
To fix CVE-2019-10113, upgrade GitLab to version 11.7.9, 11.8.4, or 11.9.2 or later.
Which GitLab versions are affected by CVE-2019-10113?
CVE-2019-10113 affects GitLab Community and Enterprise Editions prior to 11.7.8, 11.8.x before 11.8.4, and 11.9.x before 11.9.2.
What kind of issue does CVE-2019-10113 represent?
CVE-2019-10113 represents an issue related to concurrent API requests causing uncontrolled resource consumption.
Is there a workaround for CVE-2019-10113?
There are no specific workarounds for CVE-2019-10113, so it is recommended to update to a patched version.