Security readout for executives and security teams
Plain-English summary
CVE-2024-0402 is a critical GitLab CE/EE flaw that can let a logged-in user write files outside intended directories on the GitLab server when creating a workspace. For self-managed GitLab, this can threaten confidentiality, integrity, and availability. The provided sources do not show active exploitation or CISA KEV listing.
Executive priority
Treat as urgent for affected self-managed GitLab because authenticated users may gain server-level file write impact. Patch promptly, especially where many users or external users can authenticate.
Technical view
GitLab describes a CWE-22 path traversal affecting CE/EE 16.0 before 16.6.6, 16.7 before 16.7.4, and 16.8 before 16.8.1. The CVSS 3.1 score is 9.9 with network access, low complexity, low privileges, no user interaction, changed scope, and high CIA impact.
Likely exposure
Exposure is most likely in self-managed GitLab CE/EE instances running affected 16.x versions where authenticated users can create workspaces. The source bundle does not identify other affected products or unsupported branches.
Exploitation context
An attacker needs authenticated access. The vulnerability is tied to workspace creation and arbitrary file write on the GitLab server. CISA KEV is false in the provided data, and no cited source here confirms active exploitation.
Researcher notes
The public record identifies path traversal during workspace creation, not a full exploit chain. Avoid assuming unauthenticated exploitation. Review GitLab’s advisory and issue tracker for implementation details and any later vendor updates.
Mitigation direction
- Upgrade affected GitLab CE/EE to 16.8.1, 16.7.4, or 16.6.6.
- Prioritize internet-facing and broadly accessible self-managed GitLab instances.
- If immediate upgrade is not possible, check GitLab’s advisory for current guidance.
- Restrict authenticated access to trusted users until remediation is complete.
Validation and detection
- Inventory all self-managed GitLab CE/EE instances and record exact versions.
- Confirm no instance runs 16.0-16.6.5, 16.7-16.7.3, or 16.8.0.
- Verify patched instances report 16.8.1, 16.7.4, 16.6.6, or later fixed versions.
- Review workspace usage and server file-integrity signals for unusual activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-0402 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16GitLabVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://about.gitlab.com/releases/2024/01/25/critical-security-release-gitlab-16-8-1-released/CVE reference, GitLab
- GitLab Issue #437819CVE reference, GitLab · issue-tracking
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.