GitLab Community Edition/Enterprise Edition up to 16.6.5/16.7.3/16.8.0 Cargo.toml redos
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in GitLab Community Edition and Enterprise Edition up to 16.6.5/16.7.3/16.8.0. Affected is an unknown function of the file Cargo.toml. This manipulation causes redos. This vulnerability is tracked as CVE-2023-6159. The attack is possible to be carried out remotely. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability was found in GitLab Community Edition and Enterprise Edition up to 16.6.5/16.7.3/16.8.0 (Bug Tracking Software). It has been declared as problematic. Affected by this vulnerability is some unknown processing of the file Cargo.toml. The manipulation with an unknown input leads to a redos vulnerability. The CWE definition for the vulnerability is CWE-1333. The product uses a regular expression with an inefficient, possibly exponential worst-case computational complexity that consumes excessive CPU cycles. As an impact it is known to affect availability. The summary by CVE is:
An issue has been discovered in GitLab CE/EE affecting all versions from 12.7 prior to 16.6.6, 16.7 prior to 16.7.4, and 16.8 prior to 16.8.1 It was possible for an attacker to trigger a Regular Expression Denial of Service via a `Cargo.toml` containing maliciously crafted input.
The weakness was disclosed 01/26/2024 by yvvdwf as 431924. The advisory is shared at gitlab.com. This vulnerability is known as CVE-2023-6159 since 11/15/2023. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1449.003 for this issue.
Upgrading to version 16.6.6, 16.7.4 or 16.8.1 eliminates this vulnerability. The upgrade is hosted for download at about.gitlab.com.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-58409). 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: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector (GitLab Inc.): 🔍
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: RedosCWE: CWE-1333 / 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 16.6.6/16.7.4/16.8.1
Timeline
11/15/2023 🔍01/26/2024 🔍
01/26/2024 🔍
11/20/2025 🔍
Sources
Vendor: gitlab.comAdvisory: 431924
Researcher: yvvdwf
Status: Confirmed
CVE: CVE-2023-6159 (🔍)
GCVE (CVE): GCVE-0-2023-6159
GCVE (VulDB): GCVE-100-252097
EUVD: 🔍
Entry
Created: 01/26/2024 07:16Updated: 11/20/2025 06:53
Changes: 01/26/2024 07:16 (53), 11/20/2025 06:53 (16)
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.