CVE-2024-12380 is an information disclosure vulnerability in GitLab CE and EE affecting repository mirroring settings. GitLab stated that certain user inputs in the repository mirroring configuration could, when mirroring fails, potentially expose sensitive authentication information. The issue affects all versions starting from 11.5 before 17.7.7, all versions starting from 17.8 before 17.8.5, and all versions starting from 17.9 before 17.9.2. The vulnerability is associated with improper handling of sensitive data in error or failure conditions within the repository mirroring feature, resulting in possible credential exposure.
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 medium-severity GitLab-related vulnerability mentioned as one of several additional flaws that may enable remote code execution, denial of service, privilege escalation, or unauthorized access to sensitive data.
A GitLab CE/EE vulnerability in repository mirroring settings that could expose sensitive authentication information when repository mirroring fails.
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.