Loading vulnerability…
CVE-2024-3958 is a medium-severity spoofing and social-engineering vulnerability in GitLab Community Edition and Enterprise Edition. A discrepancy exists between how GitLab's web application displays certain tag names and how the Git command-line interface interprets or presents them. An attacker can abuse this ambiguity to make a malicious or untrusted repository reference appear trustworthy in the web interface, increasing the likelihood that a victim will clone code they did not intend to obtain. The issue affects GitLab CE/EE before 17.0.6, 17.1 before 17.1.4, and 17.2 before 17.2.2.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A GitLab CE/EE vulnerability that exploits ambiguous tag naming and discrepancies between web display and git CLI behavior to socially engineer users into cloning untrusted code.
UI/CLI ambiguity issue in GitLab tag naming that can be abused for social engineering to trick users into cloning untrusted code.
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.