CVE-2024-4539: Allocation of Resources Without Limits or Throttling in GitLab
An issue has been discovered in GitLab CE/EE affecting all versions starting from 15.4 prior to 16.9.7, starting from 16.10 prior to 16.10.5, and starting from 16.11 prior to 16.11.2 where abusing the API to filter branch and tags could lead to Denial of Service.
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 16.9.7Fixed in 16.10.5Fixed in 16.11.2 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 16.9.7Patch CVE-2024-4539 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 16.10.5Patch CVE-2024-4539 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 16.11.2Patch CVE-2024-4539
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2024-4539?
CVE-2024-4539 is classified as a Denial of Service vulnerability affecting GitLab versions.
How do I fix CVE-2024-4539?
To remediate CVE-2024-4539, users should upgrade GitLab to versions 16.9.7, 16.10.5, or 16.11.2 or later.
What GitLab versions are affected by CVE-2024-4539?
CVE-2024-4539 affects GitLab versions from 15.4 to 16.9.6, from 16.10.0 to 16.10.4, and from 16.11.0 to 16.11.1.
What causes CVE-2024-4539?
CVE-2024-4539 is caused by an issue in the GitLab API that can be abused to filter branches and tags, leading to a Denial of Service.
Is there a workaround for CVE-2024-4539?
There are no official workarounds for CVE-2024-4539; users are recommended to upgrade to secure versions.