Loading vulnerability…
CVE-2024-12619 is an improper access control vulnerability in GitLab Community Edition and Enterprise Edition that affects all versions from 16.0 before 17.8.6, 17.9 before 17.9.3, and 17.10 before 17.10.1. The flaw allows an internal user to gain unauthorized access to internal projects. The available information identifies the issue as an access control failure affecting project visibility enforcement, but does not provide the specific vulnerable function or code path.
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 authorization flaw in GitLab CE/EE that allows unauthorized access to internal projects.
An access control issue in GitLab CE/EE that could allow unauthorized access to internal projects (as described in the advisory).
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.