CVE-2023-6159: Inefficient Regular Expression Complexity in GitLab
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.
Security readout for executives and security teams
Plain-English summary
CVE-2023-6159 lets an authenticated attacker make vulnerable GitLab instances spend excessive processing time on a specially crafted Cargo.toml file. The main business impact is service disruption, not data theft or modification. It affects older GitLab CE/EE versions and is fixed in GitLab 16.6.6, 16.7.4, and 16.8.1.
Executive priority
Treat as a timely availability-risk patch for GitLab. Prioritize internet-facing or broadly used GitLab instances, especially where many users can create or update repositories. This is not presented as data compromise, but downtime in source control can disrupt engineering delivery.
Technical view
This is a CWE-1333 inefficient regular expression complexity issue in GitLab CE/EE. A maliciously crafted Cargo.toml can trigger Regular Expression Denial of Service. CVSS 3.1 is 6.5: network reachable, low complexity, low privileges required, no user interaction, high availability impact, no confidentiality or integrity impact.
Likely exposure
Exposure is likely for self-managed GitLab CE/EE instances running 12.7 before 16.6.6, 16.7 before 16.7.4, or 16.8 before 16.8.1. The attacker needs a low-privileged account and a path to submit content processed by GitLab.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The HackerOne and GitLab issue references are marked permissions-required, so public technical detail is limited. The known condition is a malicious Cargo.toml causing denial of service through regex complexity.
Researcher notes
Public evidence identifies the vulnerable artifact type and ReDoS class, but detailed issue and HackerOne materials require permission. Do not assume broader package-manager parsing impact beyond the cited Cargo.toml condition. CVE metadata indicates low privileges are required and no active exploitation is documented in KEV.
Mitigation direction
Upgrade GitLab CE/EE to 16.6.6, 16.7.4, 16.8.1, or later supported versions.
Review GitLab’s January 25, 2024 security release guidance.
Restrict untrusted project creation or repository content submission where upgrades are delayed.
Monitor GitLab availability and resource usage until remediation is complete.
Validation and detection
Inventory all self-managed GitLab CE/EE versions.
Flag instances in the affected version ranges.
Confirm upgraded instances report 16.6.6, 16.7.4, 16.8.1, or later.
Review recent GitLab availability incidents around repository or dependency file processing.
Check vendor guidance for any additional verification steps.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-1333: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-1333 · source CWE mapping
Inefficient Regular Expression Complexity
Inefficient Regular Expression Complexity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.