Loading vulnerability…
CVE-2024-8402 is an input validation vulnerability in GitLab Enterprise Edition affecting the Google Cloud IAM integration feature. It affects all versions from 17.2 before 17.7.7, all 17.8 releases before 17.8.5, and all 17.9 releases before 17.9.2. The flaw could allow a user with the Maintainer role to supply malicious input that is not properly validated, resulting in shell code injection through the integration workflow. The issue is limited to the Google Cloud IAM integration functionality and requires sufficient project or environment permissions associated with the Maintainer role.
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 low-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 EE input validation vulnerability in the Google Cloud IAM integration feature that could allow a Maintainer to inject shell 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.