Skip to main content

CVE-2023-3364: CWE-1333: Inefficient Regular Expression Complexity in GitLab GitLab

High
VulnerabilityCVE-2023-3364cvecve-2023-3364cwe-1333
Published: Tue Aug 01 2023 (08/01/2023, 23:36:00 UTC)
Source: CVE
Vendor/Project: GitLab
Product: GitLab

Description

An issue has been discovered in GitLab CE/EE affecting all versions starting from 8.14 before 16.0.8, all versions starting from 16.1 before 16.1.3, all versions starting from 16.2 before 16.2.2. A Regular Expression Denial of Service was possible via sending crafted payloads which use AutolinkFilter to the preview_markdown endpoint.

AI-Powered Analysis

AILast updated: 07/07/2025, 11:25:12 UTC

Technical Analysis

CVE-2023-3364 is a high-severity vulnerability affecting GitLab Community Edition (CE) and Enterprise Edition (EE) versions starting from 8.14 up to versions before 16.0.8, 16.1 up to before 16.1.3, and 16.2 up to before 16.2.2. The vulnerability is classified under CWE-1333, which relates to inefficient regular expression complexity leading to a Regular Expression Denial of Service (ReDoS). Specifically, the issue arises in the AutolinkFilter component used by the preview_markdown endpoint. An attacker can send crafted payloads containing maliciously designed regular expressions that cause excessive backtracking or computational overhead when processed by the AutolinkFilter. This results in the server consuming disproportionate CPU resources, effectively causing a denial of service by slowing down or crashing the GitLab instance. The vulnerability does not require authentication or user interaction and can be exploited remotely over the network (AV:N/AC:L/PR:N/UI:N). The CVSS v3.1 base score is 7.5, reflecting a high severity due to the potential for complete denial of service without compromising confidentiality or integrity. No known exploits in the wild have been reported yet, but the wide use of GitLab in software development environments makes this vulnerability a significant risk. The lack of patch links in the provided data suggests that users should consult official GitLab advisories for the latest patches and updates. The root cause is inefficient regular expression handling in the AutolinkFilter, which is a common source of ReDoS vulnerabilities when regex patterns are not carefully designed or limited in complexity.

Potential Impact

For European organizations, the impact of CVE-2023-3364 can be substantial, especially for those relying heavily on GitLab for source code management, CI/CD pipelines, and collaborative development. A successful ReDoS attack can lead to service outages, disrupting development workflows and delaying software releases. This downtime can affect productivity and potentially lead to financial losses, especially for organizations with tight release schedules or those providing software as a service. Additionally, prolonged denial of service could indirectly impact the integrity of development processes if teams resort to insecure workarounds or alternative tools. Since GitLab often hosts sensitive source code and project management data, even though confidentiality and integrity are not directly compromised by this vulnerability, the availability impact alone can have cascading effects on business operations and security posture. Furthermore, the vulnerability could be exploited as part of a broader attack strategy to distract or exhaust IT resources. Given that no authentication is required, attackers can launch these attacks from external networks, increasing the threat surface for organizations with publicly accessible GitLab instances.

Mitigation Recommendations

To mitigate CVE-2023-3364, European organizations should take the following specific actions: 1) Immediately identify and inventory all GitLab instances, including self-hosted and cloud deployments, to assess exposure. 2) Apply the latest GitLab patches or upgrade to versions 16.0.8, 16.1.3, 16.2.2, or later where the vulnerability is fixed. If immediate patching is not feasible, consider temporarily disabling or restricting access to the preview_markdown endpoint or the AutolinkFilter feature to reduce attack surface. 3) Implement rate limiting and web application firewall (WAF) rules to detect and block suspicious payloads targeting the preview_markdown endpoint, focusing on unusually complex or large markdown requests. 4) Monitor GitLab server performance metrics and logs for signs of abnormal CPU usage or request patterns indicative of ReDoS attempts. 5) Restrict public access to GitLab instances where possible, enforcing network segmentation and VPN access to reduce exposure. 6) Educate development and security teams about the risk of ReDoS and encourage reporting of unusual service behavior. 7) Regularly review and update incident response plans to include scenarios involving denial of service due to application-layer vulnerabilities like ReDoS.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
GitLab
Date Reserved
2023-06-22T07:15:42.079Z
Cisa Enriched
true
Cvss Version
3.1
State
PUBLISHED

Threat ID: 682ea68a0acd01a249253f30

Added to database: 5/22/2025, 4:22:34 AM

Last enriched: 7/7/2025, 11:25:12 AM

Last updated: 7/28/2025, 6:28:54 PM

Views: 12

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats