CVE-2024-5430: Improper Access Control in GitLab
An issue was discovered in GitLab CE/EE affecting all versions starting from 16.10 prior to 16.11.5, starting from 17.0 prior to 17.0.3, and starting from 17.1 prior to 17.1.1, which allows a project maintainer can delete the merge request approval policy via graphQL.
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.11.5Fixed in 17.0.3Fixed in 17.1.1 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 17.1.1 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 17.0.3 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 16.11.5 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Patch CVE-2024-5430
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2024-5430?
CVE-2024-5430 is classified as a medium severity vulnerability that allows project maintainers to delete merge request approval policies via graphQL.
How do I fix CVE-2024-5430?
To fix CVE-2024-5430, upgrade GitLab CE/EE to version 16.11.5, 17.0.3, or 17.1.1 or later.
Which versions of GitLab are affected by CVE-2024-5430?
CVE-2024-5430 affects GitLab CE/EE versions from 16.10 to 16.11.4, 17.0 to 17.0.2, and 17.1.0.
Can project maintainers exploit CVE-2024-5430?
Yes, project maintainers can exploit CVE-2024-5430 to delete merge request approval policies without proper authorization.
Is there a workaround for CVE-2024-5430?
There is no official workaround for CVE-2024-5430; the recommended action is to update to the patched versions immediately.