CVE-2022-2185 is a critical vulnerability in GitLab affecting versions 14.0 through 14.10.4, 15.0 through 15.0.3, and 15.1 through 15.1.0. The flaw allows an authenticated user with project import permissions to import a specially crafted project archive, which can trigger remote code execution on the GitLab server. The vulnerability arises from insufficient validation or sanitization of project import data, allowing embedded malicious code to be executed during the import process.
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 contains a proof-of-concept exploit for CVE-2022-2185, a vulnerability in GitLab that allows authenticated remote code execution via the project import feature. The exploit consists of a Go program (main.go) that acts as a man-in-the-middle (MITM) HTTP proxy, listening on 0.0.0.0:8100. The proxy intercepts POST requests to /api/graphql, and if the request body contains the configured project name, it injects a malicious response with a crafted 'import_source' field containing a shell command (default: '/bin/sleep inf', but can be changed). The README.md provides setup instructions, including how to configure the exploit, run the proxy, and manipulate the import request to trigger the vulnerability. The exploit requires the attacker to have authenticated access to a GitLab instance and the ability to intercept and modify HTTP requests during the import process. The main exploit capability is arbitrary command execution on the GitLab server. The repository is structured simply, with a single Go source file and a README with usage instructions.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.