What is the severity of CVE-2019-9220?

CVE-2019-9220 is classified as a medium severity vulnerability due to its potential for uncontrolled resource consumption.

How do I fix CVE-2019-9220?

Fix CVE-2019-9220 by upgrading to GitLab Community or Enterprise Edition versions 11.6.10, 11.7.6, or 11.8.1 or later.

What systems are affected by CVE-2019-9220?

CVE-2019-9220 affects GitLab Community and Enterprise Edition versions prior to 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1.

What are the potential impacts of CVE-2019-9220?

The potential impacts of CVE-2019-9220 include denial of service due to resource exhaustion.

Is there a workaround for CVE-2019-9220?

There are no known workarounds for CVE-2019-9220; upgrading to the fixed versions is recommended.

Vulnerability/
CVE-2019-9220

high

7.5

CWE

400

17/4/2019

21/11/2024

CVE-2019-9220

First published: Wed Apr 17 2019(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition before 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1. It allows Uncontrolled Resource Consumption.

Credit: cve@mitre.org cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	<11.6.10
GitLab	<11.6.10
GitLab	>=11.7.0<11.7.6
GitLab	>=11.7.0<11.7.6
GitLab	>=11.8.0<11.8.1
GitLab	>=11.8.0<11.8.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-9220?
CVE-2019-9220 is classified as a medium severity vulnerability due to its potential for uncontrolled resource consumption.
How do I fix CVE-2019-9220?
Fix CVE-2019-9220 by upgrading to GitLab Community or Enterprise Edition versions 11.6.10, 11.7.6, or 11.8.1 or later.
What systems are affected by CVE-2019-9220?
CVE-2019-9220 affects GitLab Community and Enterprise Edition versions prior to 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1.
What are the potential impacts of CVE-2019-9220?
The potential impacts of CVE-2019-9220 include denial of service due to resource exhaustion.
Is there a workaround for CVE-2019-9220?
There are no known workarounds for CVE-2019-9220; upgrading to the fixed versions is recommended.

agent/type
agent/references
agent/weakness
agent/severity
agent/description
collector/mitre-cve
source/MITRE
agent/first-publish-date
agent/last-modified-date
agent/author
agent/softwarecombine
agent/event
agent/source
agent/tags
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/software-canonical-lookup-request
collector/nvd-index
vendor/gitlab
canonical/gitlab
version/gitlab/11.7.0
version/gitlab/11.8.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-9220?
CVE-2019-9220 is classified as a medium severity vulnerability due to its potential for uncontrolled resource consumption.
How do I fix CVE-2019-9220?
Fix CVE-2019-9220 by upgrading to GitLab Community or Enterprise Edition versions 11.6.10, 11.7.6, or 11.8.1 or later.
What systems are affected by CVE-2019-9220?
CVE-2019-9220 affects GitLab Community and Enterprise Edition versions prior to 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1.
What are the potential impacts of CVE-2019-9220?
The potential impacts of CVE-2019-9220 include denial of service due to resource exhaustion.
Is there a workaround for CVE-2019-9220?
There are no known workarounds for CVE-2019-9220; upgrading to the fixed versions is recommended.