CVE-2024-6385 is a critical authorization flaw in GitLab Community Edition and Enterprise Edition that affects versions starting from 15.8 before 16.11.6, starting from 17.0 before 17.0.4, and starting from 17.1 before 17.1.2. Under certain circumstances, the issue allows an attacker to trigger a CI/CD pipeline as another user. Available information ties the flaw to GitLab importer-related functionality and user contribution or membership mapping behavior, where imported activity could be attributed to the wrong user identity. This results in pipeline execution occurring in the security context of a different user rather than the attacker’s own account.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A previously discovered vulnerability affecting GitLab import functionality that motivated GitLab to redesign importer user contribution mapping.
A critical GitLab CE/EE vulnerability that allows an attacker to trigger a pipeline as another user under certain circumstances.
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.