Loading vulnerability…
CVE-2024-0402 is a critical arbitrary file write vulnerability in GitLab Community Edition and Enterprise Edition Workspaces. It affects versions 16.0 through before 16.5.8, 16.6 through before 16.6.6, 16.7 through before 16.7.4, and 16.8 through before 16.8.1. The flaw allows an authenticated user to write files to arbitrary locations on the GitLab server during workspace creation. Available technical analysis indicates the issue is reachable through processing of workspace devfile content and involves insufficient restriction of file extraction paths in the devfile handling chain, enabling path traversal during archive decompression and resulting in server-side arbitrary file write.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a weaponized exploit for CVE-2024-0402, a path traversal vulnerability in Gitlab EE's devfile registry support (prior to registry-support v1.1.0). The exploit is delivered as a malicious devfile registry Docker image, which serves a crafted Node.js stack containing an 'archive.tar' file. This tarball, created with evilarc.py, is designed to exploit the path traversal and overwrite the '/var/opt/gitlab/.ssh/authorized_keys' file on a vulnerable Gitlab server. The attacker's SSH public key (ssh-keys/pockey.pub) is injected, allowing remote shell access as the 'git' user using the provided private key (ssh-keys/pockey). The repository includes all necessary files: Dockerfile for building the registry, devfile and stack YAMLs, SSH key pair, and documentation. The attack vector is network-based, requiring the victim Gitlab instance to fetch devfiles from the attacker's registry. The exploit is operational and provides a working post-exploitation shell if the target is properly configured and vulnerable.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A GitLab Workspaces vulnerability chain in which a YAML parser differential bypasses validation of the devfile parent option, leading GitLab to fetch content from a malicious devfile registry and trigger a path traversal in archive decompression, resulting in arbitrary file write on the GitLab server.
GitLab arbitrary file write vulnerability that allows an authenticated user to write files to arbitrary locations on the GitLab server during workspace creation, and can be used to deploy malware.
A critical GitLab arbitrary file write vulnerability that allows an authenticated user to write files to arbitrary locations on the GitLab server during workspace creation, and it may be used to spread malware.
A critical arbitrary file write vulnerability in GitLab CE/EE that allows an authenticated user to write files to arbitrary locations on the GitLab server during workspace creation.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.