CVE-2024-9367: Allocation of Resources Without Limits or Throttling in GitLab
An issue was discovered in GitLab CE/EE affecting all versions starting from 13.9 before 17.4.6, 17.5 before 17.5.4, and 17.6 before 17.6.2, that allows an attacker to cause uncontrolled CPU consumption, potentially leading to a Denial of Service (DoS) condition while parsing templates to generate changelogs.
Other sources
An issue was discovered in GitLab CE/EE affecting all versions starting from 13.9 before 17.4.6, 17.5 before 17.5.4, and 17.6 before 17.6.2, that allows an attacker to cause uncontrolled resource consumption, potentially leading to a Denial of Service (DoS) condition while parsing templates to generate changelogs. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L, 4.3). It is now mitigated in the latest release and is assigned CVE-2024-9367.
— GitLab
Affected Software
Remediation
Information
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2024-9367?
CVE-2024-9367 has a high severity level due to its potential to cause Denial of Service (DoS) by uncontrolled CPU consumption.
How do I fix CVE-2024-9367?
To fix CVE-2024-9367, upgrade GitLab CE/EE to versions 17.4.6, 17.5.4, or 17.6.2 or later.
What versions are affected by CVE-2024-9367?
CVE-2024-9367 affects GitLab CE/EE versions from 13.9 up to but not including 17.4.6, 17.5, and 17.6 up to but not including their respective latest secure versions.
What type of attack is CVE-2024-9367 associated with?
CVE-2024-9367 is associated with Denial of Service (DoS) attacks due to excessive CPU consumption during template parsing.
Is my GitLab installation vulnerable to CVE-2024-9367?
If your GitLab installation is running a version between 13.9 and 17.4.6, 17.5 before 17.5.4, or 17.6 before 17.6.2, it is vulnerable to CVE-2024-9367.