GitLab Community/Enterprise up to 11.6.9/11.7.5/11.8.0 resource management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in GitLab Community and Enterprise up to 11.6.9/11.7.5/11.8.0. It has been classified as problematic. This issue affects some unknown processing. Performing a manipulation results in resource management. This vulnerability is reported as CVE-2019-9220. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability was found in GitLab Community and Enterprise up to 11.6.9/11.7.5/11.8.0 (Bug Tracking Software). It has been classified as problematic. This affects an unknown code block. The manipulation with an unknown input leads to a resource management vulnerability. CWE is classifying the issue as CWE-399. This is going to have an impact on availability. The summary by CVE is:
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.
The bug was discovered 03/04/2019. The weakness was disclosed 04/17/2019 (Website). It is possible to read the advisory at about.gitlab.com. This vulnerability is uniquely identified as CVE-2019-9220 since 02/28/2019. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 44 days. During that time the estimated underground price was around $0-$5k. The commercial vulnerability scanner Qualys is able to test this issue with plugin 371751 (GitLab Multiple Security Vulnerability).
Upgrading to version 11.6.10, 11.7.6 or 11.8.1 eliminates this vulnerability.
The entries VDB-133457, VDB-133458, VDB-133459 and VDB-133460 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 11.0
- 11.1
- 11.2
- 11.3
- 11.4
- 11.5
- 11.6
- 11.6.0
- 11.6.1
- 11.6.2
- 11.6.3
- 11.6.4
- 11.6.5
- 11.6.6
- 11.6.7
- 11.6.8
- 11.6.9
- 11.7
- 11.7.0
- 11.7.1
- 11.7.2
- 11.7.3
- 11.7.4
- 11.7.5
- 11.8.0
License
Website
- Vendor: https://gitlab.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Resource managementCWE: CWE-399 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Community/Enterprise 11.6.10/11.7.6/11.8.1
Timeline
02/28/2019 🔍03/04/2019 🔍
04/17/2019 🔍
04/17/2019 🔍
08/29/2023 🔍
Sources
Vendor: gitlab.comAdvisory: 55653
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2019-9220 (🔍)
GCVE (CVE): GCVE-0-2019-9220
GCVE (VulDB): GCVE-100-133467
See also: 🔍
Entry
Created: 04/17/2019 23:23Updated: 08/29/2023 16:04
Changes: 04/17/2019 23:23 (60), 05/30/2020 11:07 (2), 08/29/2023 16:04 (4)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.