CVE-2024-4011: Improper Access Control in GitLab
An issue was discovered in GitLab CE/EE affecting all versions starting from 16.1 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 non-project member to promote key results to objectives.
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
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2024-4011?
CVE-2024-4011 is considered a moderate severity vulnerability that allows non-project members to promote key results to objectives in GitLab.
How do I fix CVE-2024-4011?
To fix CVE-2024-4011, upgrade GitLab to version 16.11.5 or 17.0.3 or later versions.
Which versions of GitLab are affected by CVE-2024-4011?
CVE-2024-4011 affects GitLab CE/EE versions starting from 16.1 up to 16.11.5, from 17.0 to 17.0.3, and 17.1.0.
Who is impacted by CVE-2024-4011?
Users who are non-project members in GitLab are impacted by CVE-2024-4011.
What type of vulnerability is CVE-2024-4011?
CVE-2024-4011 is a security vulnerability that allows unauthorized privilege escalation in GitLab.