CVE-2024-10307 is an uncontrolled resource consumption vulnerability in GitLab Community Edition and Enterprise Edition. It affects all versions from 12.10 before 17.8.6, 17.9 before 17.9.3, and 17.10 before 17.10.1. The issue is triggered by a maliciously crafted Terraform file associated with a merge request. When the merge request is viewed, GitLab processes the crafted file in a way that can cause uncontrolled CPU consumption. The vulnerability is a denial-of-service condition in the merge request viewing workflow rather than a memory corruption or code execution flaw.
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 uncontrolled resource consumption vulnerability in GitLab CE/EE where a crafted Terraform file can trigger excessive CPU usage when a merge request is viewed.
A denial-of-service style issue in GitLab CE/EE where a crafted Terraform file could trigger uncontrolled CPU consumption when viewing a merge request.
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.