GitLab Community Edition/Enterprise Edition up to 11.11.5/12.0.3/12.1.1 Epic Comment resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in GitLab Community Edition and Enterprise Edition up to 11.11.5/12.0.3/12.1.1. It has been rated as problematic. Affected by this vulnerability is an unknown functionality of the component Epic Comment Handler. Performing a manipulation results in resource consumption. This vulnerability is reported as CVE-2019-5472. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is advised.
Details
A vulnerability, which was classified as problematic, was found in GitLab Community Edition and Enterprise Edition up to 11.11.5/12.0.3/12.1.1 (Bug Tracking Software). This affects an unknown function of the component Epic Comment Handler. The manipulation with an unknown input leads to a resource consumption vulnerability. CWE is classifying the issue as CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. This is going to have an impact on availability. The summary by CVE is:
An authorization issue was discovered in Gitlab versions < 12.1.2, < 12.0.4, and < 11.11.6 that prevented owners and maintainer to delete epic comments.
The weakness was disclosed 01/28/2020. This vulnerability is uniquely identified as CVE-2019-5472 since 01/04/2019. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
Upgrading to version 11.11.6, 12.0.4 or 12.1.2 eliminates this vulnerability.
The entries VDB-149456, VDB-149455, VDB-149454 and VDB-149453 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
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 consumptionCWE: CWE-400 / 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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Community Edition/Enterprise Edition 11.11.6/12.0.4/12.1.2
Timeline
01/04/2019 🔍01/28/2020 🔍
01/28/2020 🔍
03/27/2024 🔍
Sources
Vendor: gitlab.comAdvisory: 11381
Status: Not defined
CVE: CVE-2019-5472 (🔍)
GCVE (CVE): GCVE-0-2019-5472
GCVE (VulDB): GCVE-100-149457
See also: 🔍
Entry
Created: 01/28/2020 14:39Updated: 03/27/2024 07:02
Changes: 01/28/2020 14:39 (38), 01/28/2020 14:44 (18), 03/27/2024 07:02 (19)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.