GitLab Community Edition/Enterprise Edition up to 11.11.7/12.0.5/12.0/12.1.5 Command-Line Flag argument injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in GitLab Community Edition and Enterprise Edition up to 11.11.7/12.0.5/12.0/12.1.5. Affected by this issue is some unknown functionality of the component Command-Line Flag Handler. The manipulation results in argument injection. This vulnerability was named CVE-2019-14944. The attack may be performed from remote. There is no available exploit. Upgrading the affected component is advised.
Details
A vulnerability, which was classified as critical, was found in GitLab Community Edition and Enterprise Edition up to 11.11.7/12.0.5/12.0/12.1.5 (Bug Tracking Software). Affected is an unknown function of the component Command-Line Flag Handler. The manipulation with an unknown input leads to a argument injection vulnerability. CWE is classifying the issue as CWE-88. The product constructs a string for a command to be executed by a separate component
in another control sphere, but it does not properly delimit the
intended arguments, options, or switches within that command string. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
An issue was discovered in GitLab Community and Enterprise Edition before 11.11.8, 12 before 12.0.6, and 12.1 before 12.1.6. Gitaly allows injection of command-line flags. This sometimes leads to privilege escalation or remote code execution.
The weakness was presented 04/16/2023 as 1801. The advisory is shared for download at gitlab.com. This vulnerability is traded as CVE-2019-14944 since 08/11/2019. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1059.
Upgrading to version 11.11.8, 12.0.6, 12.1 or 12.1.6 eliminates this vulnerability. The upgrade is hosted for download at about.gitlab.com.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
- 11.11.0
- 11.11.1
- 11.11.2
- 11.11.3
- 11.11.4
- 11.11.5
- 11.11.6
- 11.11.7
- 12.0
- 12.0.0
- 12.0.1
- 12.0.2
- 12.0.3
- 12.0.4
- 12.0.5
- 12.1.0
- 12.1.1
- 12.1.2
- 12.1.3
- 12.1.4
- 12.1.5
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.2
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.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: 🔍
Exploiting
Class: Argument injectionCWE: CWE-88 / CWE-74 / CWE-707
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.8/12.0.6/12.1/12.1.6
Timeline
08/11/2019 🔍04/16/2023 🔍
04/16/2023 🔍
05/05/2023 🔍
Sources
Vendor: gitlab.comAdvisory: 1801
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2019-14944 (🔍)
GCVE (CVE): GCVE-0-2019-14944
GCVE (VulDB): GCVE-100-226128
Entry
Created: 04/16/2023 07:43Updated: 05/05/2023 11:06
Changes: 04/16/2023 07:43 (44), 05/05/2023 11:06 (11)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
in this case and for the next cves, We would like to point out that the official NVD Nist cpe is "gitlab:gitlab". The sw_edition must not be written in the field belonging to the product.
Best Regards,
TEAM CERT
Want to know what is going to be exploited?
We predict KEV entries!