Loading vulnerability…
CVE-2024-2880 is an authorization flaw in GitLab Community Edition and Enterprise Edition affecting versions 16.5 before 16.11.6, 17.0 before 17.0.4, and 17.1 before 17.1.2. A user granted the admin_group_member custom role permission could ban group members. The issue reflects insufficient restriction of privileged group-member management actions, allowing a role with that permission to perform a banning operation that should not have been permitted under the intended authorization model.
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.
admin_group_member custom role permission to ban members of a GitLab group. This can disrupt legitimate user access and group administration, and may be used to interfere with collaboration or selectively deny service to targeted group members. Based on the available information, the impact is limited to unauthorized group member banning rather than code execution or broader instance compromise.If you can’t patch tonight, do this now.
admin_group_member permission, especially for users who do not require sensitive group membership administration capabilities. Monitor group membership and ban actions for unauthorized changes, and restrict access to privileged group-management functions until patched versions can be deployed. Complete mitigation requires upgrading to a fixed version.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.
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.