CVE-2024-11931: Insufficient Granularity of Access Control in GitLab
An issue has been discovered in GitLab CE/EE affecting all versions starting from 17.0 prior to 17.6.4, from 17.7 prior to 17.7.3, and from 17.8 prior to 17.8.1. Under certain conditions, it may have been possible for users with developer role to exfiltrate protected CI variables via CI lint.
Other sources
An issue has been discovered in GitLab CE/EE affecting all versions starting from 17.0 prior to 17.6.4, from 17.7 prior to 17.7.3, and from 17.8 prior to 17.8.1. Under certain conditions, it may have been possible for users with developer role to exfiltrate protected CI/CD variables via CI lint. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N, 6.4). It is now mitigated in the latest release and is assigned CVE-2024-11931.
— GitLab
Affected Software
Remediation
Information
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2024-11931?
CVE-2024-11931 is classified as a high-severity vulnerability affecting specific versions of GitLab CE/EE.
How do I fix CVE-2024-11931?
To mitigate CVE-2024-11931, upgrade your GitLab CE/EE installation to version 17.6.4, 17.7.3, or 17.8.1 or later.
Who is affected by CVE-2024-11931?
CVE-2024-11931 affects users with developer role in GitLab CE/EE versions starting from 17.0 up to 17.6.4, 17.7 up to 17.7.3, and 17.8 up to 17.8.1.
What kind of vulnerability is CVE-2024-11931?
CVE-2024-11931 is a security vulnerability related to the unauthorized exfiltration of protected CI variables.
Can I check if my GitLab instance is vulnerable to CVE-2024-11931?
You can determine if your GitLab instance is vulnerable to CVE-2024-11931 by verifying the version against the specified affected versions.