CVE-2024-2874: Allocation of Resources Without Limits or Throttling in GitLab
An issue has been discovered in GitLab CE/EE affecting all versions before 16.10.6, version 16.11 before 16.11.3, and 17.0 before 17.0.1. A runner registered with a crafted description has the potential to disrupt the loading of targeted GitLab web resources.
Other sources
An issue has been discovered in GitLab CE/EE affecting all versions up to 16.10.6, versions 16.11 up to 16.11.3, and 17.0 up to 17.0.1. A runner registered with a crafted description has the potential to disrupt the loading of targeted GitLab web resources. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, 6.5). It is now mitigated in the latest release and is assigned CVE-2024-2874.
— GitLab
Affected Software
Remediation
Information
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2024-2874?
CVE-2024-2874 is classified as a high-severity vulnerability.
Which versions of GitLab are affected by CVE-2024-2874?
CVE-2024-2874 affects all versions before 16.10.6, 16.11 versions before 16.11.3, and 17.0 version before 17.0.1.
How do I fix CVE-2024-2874?
To fix CVE-2024-2874, upgrade your GitLab instance to version 16.10.6 or later, 16.11.3 or later, or 17.0.1 or later.
What is the impact of CVE-2024-2874 on GitLab?
CVE-2024-2874 allows a malicious runner with a crafted description to disrupt the loading of GitLab web resources.
Can CVE-2024-2874 be exploited remotely?
Yes, CVE-2024-2874 can potentially be exploited remotely by attackers who register a malicious runner.