Cyber Resilience

CVE-2024-8124

Gitlab 16.4.0 – 17.1.7

Published
12 September 2024
Modified
21 November 2024
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.40 98th percentile
Risk Priority 75 floored blend · peak EPSS

Summary

CVE-2024-8124 is a high-severity Inefficient Regular Expression Complexity (CWE-1333) vulnerability in Gitlab Gitlab. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked in the top 2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-8124 is a denial-of-service vulnerability in GitLab Community Edition and Enterprise Edition. It affects all versions from 16.4 up to but not including 17.1.7, from 17.2 up to but not including 17.2.5, and from 17.3 up to but not including 17.3.2. The flaw, tracked under CWE-1333, can be triggered by a specially crafted POST request that exhausts server resources and produces a high availability impact according to its CVSS 7.5 score.

An unauthenticated attacker with network access can send the malicious POST request to induce the denial-of-service condition. No user interaction or credentials are required, allowing remote exploitation that disrupts GitLab service availability without affecting confidentiality or integrity.

GitLab addressed the issue in the September 2024 patch release covering versions 17.1.7, 17.2.5, and 17.3.2. Administrators are advised to upgrade to one of the fixed releases; the corresponding security issue and HackerOne report provide additional technical context for the fix.

The associated EPSS score reached a modest peak of 0.0584 and has since declined to 0.0455, indicating limited and non-persistent exploitation interest after disclosure.

EU & UK References

Vulnerability Data

An issue was discovered in GitLab CE/EE affecting all versions starting from 16.4 prior to 17.1.7, starting from 17.2 prior to 17.2.5, starting from 17.3 prior to 17.3.2 which could cause Denial of Service via sending a specific POST request.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-6688Same product: Gitlab Gitlab
CVE-2023-3994Same product: Gitlab Gitlab
CVE-2024-2651Same product: Gitlab Gitlab
CVE-2024-2829Same product: Gitlab Gitlab
CVE-2023-6682Same product: Gitlab Gitlab
CVE-2023-3424Same product: Gitlab Gitlab
CVE-2023-2198Same product: Gitlab Gitlab
CVE-2023-3909Same product: Gitlab Gitlab
CVE-2024-4025Same product: Gitlab Gitlab
CVE-2024-1495Same product: Gitlab Gitlab

Affected Assets

gitlab
gitlab
16.4.0 — 17.1.7 · 16.4.0 — 17.1.7 · 17.2.0 — 17.2.5

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover inefficient regex patterns via performance or static analysis.

Development standards and tools can require safe regex construction and forbid known exponential patterns.

Denial-of-service protections limit resource exhaustion caused by expensive regex evaluation.

Input validation can constrain data that would otherwise trigger worst-case regex complexity.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent inefficient regex via reviews, static analysis, and safe libraries.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover ReDoS issues in existing code but do not stop their introduction.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect and reject regex patterns with exponential worst-case complexity.

prevents

Secure development lifecycle mandates review of algorithmic efficiency, directly addressing ReDoS-prone regex.

prevents

Application security requirements can specify input-validation rules that limit regex complexity.

prevents

Secure architecture principles encourage avoidance of computationally expensive constructs such as catastrophic backtracking.

prevents

Secure coding standards explicitly prohibit or limit the use of inefficient regular expressions.

References