CVE-2024-2800 is a regular expression denial-of-service vulnerability in GitLab Community Edition and Enterprise Edition. The flaw is in RefMatcher logic used when matching branch names with wildcard patterns. A crafted branch name or matching input can trigger excessive regular-expression backtracking, causing disproportionate CPU consumption during evaluation. The issue affects GitLab CE/EE versions from 11.3 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 regular expression denial-of-service vulnerability in GitLab CE/EE RefMatcher caused by regex backtracking when matching wildcard branch names.
Regular expression denial-of-service (ReDoS) in GitLab RefMatcher wildcard branch-name matching due to regex backtracking.
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.