CVE-2024-10307: Allocation of Resources Without Limits or Throttling in GitLab
An issue has been discovered in GitLab EE/CE affecting all versions from 12.10 before 17.8.6, 17.9 before 17.9.3, and 17.10 before 17.10.1. A maliciously crafted file can cause uncontrolled CPU consumption when viewing the associated merge request.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 17.8.6Fixed in 17.9.3Fixed in 17.10.1 - Upgrade
Upgrade
GitLab EE/CEto a version that resolves this vulnerability.Fixed in 17.8.6 - Upgrade
Upgrade
GitLab EE/CEto a version that resolves this vulnerability.Fixed in 17.9.3 - Upgrade
Upgrade
GitLab EE/CEto a version that resolves this vulnerability.Fixed in 17.10.1
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2024-10307?
CVE-2024-10307 is considered a high severity vulnerability due to its ability to cause uncontrolled CPU consumption.
How do I fix CVE-2024-10307?
To fix CVE-2024-10307, you should upgrade GitLab EE/CE to version 17.8.6, 17.9.3, or 17.10.1 or later.
Which versions are affected by CVE-2024-10307?
CVE-2024-10307 affects GitLab EE/CE versions from 12.10 up to but not including 17.8.6, 17.9 up to but not including 17.9.3, and 17.10 up to but not including 17.10.1.
What type of attacks can be executed using CVE-2024-10307?
CVE-2024-10307 can be exploited by uploading a maliciously crafted file that may lead to denial-of-service through excessive CPU consumption.
Is there a patch available for CVE-2024-10307?
Yes, GitLab has released patches for CVE-2024-10307 in the latest updates for the affected versions.