GitLab Enterprise Edition up to 12.3.8/12.4.5/12.5.3 Maven Package Registry Parameter path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in GitLab Enterprise Edition up to 12.3.8/12.4.5/12.5.3. This impacts an unknown function of the component Maven Package Registry. The manipulation as part of Parameter leads to path traversal. This vulnerability is traded as CVE-2019-19628. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in GitLab Enterprise Edition up to 12.3.8/12.4.5/12.5.3 (Bug Tracking Software) and classified as critical. This issue affects an unknown functionality of the component Maven Package Registry. The manipulation as part of a Parameter leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In GitLab EE 11.3 through 12.5.3, 12.4.5, and 12.3.8, insufficient parameter sanitization for the Maven package registry could lead to privilege escalation and remote code execution vulnerabilities under certain conditions.
The weakness was shared 01/05/2020 (Website). The advisory is shared at about.gitlab.com. The identification of this vulnerability is CVE-2019-19628 since 12/06/2019. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1006 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entry VDB-148290 is related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- 12.3.0
- 12.3.1
- 12.3.2
- 12.3.3
- 12.3.4
- 12.3.5
- 12.3.6
- 12.3.7
- 12.3.8
- 12.4.0
- 12.4.1
- 12.4.2
- 12.4.3
- 12.4.4
- 12.4.5
- 12.5.0
- 12.5.1
- 12.5.2
- 12.5.3
License
Website
- Vendor: https://gitlab.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: Path traversalCWE: CWE-22
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/06/2019 🔍01/05/2020 🔍
01/06/2020 🔍
01/06/2020 🔍
Sources
Vendor: gitlab.comAdvisory: about.gitlab.com
Status: Not defined
CVE: CVE-2019-19628 (🔍)
GCVE (CVE): GCVE-0-2019-19628
GCVE (VulDB): GCVE-100-148289
See also: 🔍
Entry
Created: 01/06/2020 08:08Updated: 01/06/2020 08:13
Changes: 01/06/2020 08:08 (39), 01/06/2020 08:13 (18)
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.