What is the severity of CVE-2019-13007?

CVE-2019-13007 is considered a high severity vulnerability due to its potential for resource depletion.

How do I fix CVE-2019-13007?

To fix CVE-2019-13007, update to GitLab Community or Enterprise Edition version 12.0.3 or later.

Who is affected by CVE-2019-13007?

CVE-2019-13007 affects users of GitLab Community and Enterprise Editions from version 11.11 to 12.0.2.

What type of vulnerability is CVE-2019-13007?

CVE-2019-13007 is classified as a resource depletion vulnerability leading to uncontrolled resource consumption.

When was CVE-2019-13007 disclosed?

CVE-2019-13007 was disclosed in July 2019 with the release of GitLab 12.0.3.

Vulnerability/
CVE-2019-13007

medium

4.9

CWE

400

10/3/2020

4/8/2024

CVE-2019-13007

First published: Tue Mar 10 2020(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition 11.11 through 12.0.2. When an admin enabled one of the service templates, it was triggering an action that leads to resource depletion. It allows Uncontrolled Resource Consumption.

Credit: cve@mitre.org

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

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-13007?
CVE-2019-13007 is considered a high severity vulnerability due to its potential for resource depletion.
How do I fix CVE-2019-13007?
To fix CVE-2019-13007, update to GitLab Community or Enterprise Edition version 12.0.3 or later.
Who is affected by CVE-2019-13007?
CVE-2019-13007 affects users of GitLab Community and Enterprise Editions from version 11.11 to 12.0.2.
What type of vulnerability is CVE-2019-13007?
CVE-2019-13007 is classified as a resource depletion vulnerability leading to uncontrolled resource consumption.
When was CVE-2019-13007 disclosed?
CVE-2019-13007 was disclosed in July 2019 with the release of GitLab 12.0.3.

agent/references
agent/type
agent/severity
agent/weakness
agent/author
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/11.11
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-13007?
CVE-2019-13007 is considered a high severity vulnerability due to its potential for resource depletion.
How do I fix CVE-2019-13007?
To fix CVE-2019-13007, update to GitLab Community or Enterprise Edition version 12.0.3 or later.
Who is affected by CVE-2019-13007?
CVE-2019-13007 affects users of GitLab Community and Enterprise Editions from version 11.11 to 12.0.2.
What type of vulnerability is CVE-2019-13007?
CVE-2019-13007 is classified as a resource depletion vulnerability leading to uncontrolled resource consumption.
When was CVE-2019-13007 disclosed?
CVE-2019-13007 was disclosed in July 2019 with the release of GitLab 12.0.3.