CVE-2024-6324: Inefficient Algorithmic Complexity in GitLab
An issue was discovered in GitLab CE/EE affecting all versions starting from 15.7 prior to 17.5.5, starting from 17.6 prior to 17.6.3, and starting from 17.7 prior to 17.7.1. It was possible to trigger a DoS by creating cyclic references between epics.
Other sources
An issue was discovered in GitLab CE/EE affecting all versions starting from 15.7 prior to 17.6.4, starting from 17.7 prior to 17.7.3, and starting from 17.8 prior to 17.8.1. It was possible to trigger a DoS by creating cyclic references between epics. 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-6324.
— GitLab
Affected Software
Remediation
Information
Event History
Frequently Asked Questions
What is the severity of CVE-2024-6324?
CVE-2024-6324 is classified as a denial-of-service vulnerability affecting certain versions of GitLab CE/EE.
How do I fix CVE-2024-6324?
To fix CVE-2024-6324, upgrade your GitLab CE/EE to version 17.5.5, 17.6.3, or 17.7.1 or later.
Which versions of GitLab are affected by CVE-2024-6324?
CVE-2024-6324 affects GitLab CE/EE versions starting from 15.7 to prior versions of 17.5.5, 17.6 to prior versions of 17.6.3, and 17.7 to prior versions of 17.7.1.
What kind of issue does CVE-2024-6324 cause in GitLab?
CVE-2024-6324 allows attackers to trigger a denial-of-service by creating cyclic references between epics.
Is there a workaround for CVE-2024-6324 if I cannot upgrade immediately?
Currently, there are no known workarounds for CVE-2024-6324, so upgrading is recommended to mitigate the risk.