CVE-2019-9220: High severity gitlab vulnerability
Published 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.
Affected Software
6 affected components
GitLab GitLab<11.6.10
GitLab GitLab<11.6.10
GitLab GitLab>=11.7.0<11.7.6
GitLab GitLab>=11.7.0<11.7.6
GitLab GitLab>=11.8.0<11.8.1
GitLab GitLab>=11.8.0<11.8.1
Event History
Apr 17, 2019
CVE Published
via MITRE·04:52 PM
Data Sourced
via MITRE·04:52 PM
Description
Data Sourced
via NVD·05:29 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
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.
2
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.
3
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.
4
What are the potential impacts of CVE-2019-9220?
The potential impacts of CVE-2019-9220 include denial of service due to resource exhaustion.
5
Is there a workaround for CVE-2019-9220?
There are no known workarounds for CVE-2019-9220; upgrading to the fixed versions is recommended.