First published: Thu Sep 12 2024(Updated: )
A privilege escalation issue has been discovered in GitLab EE affecting all versions starting from 16.6 prior to 17.1.7, from 17.2 prior to 17.2.5, and from 17.3 prior to 17.3.2. A user assigned the Admin Group Member custom role could have escalated their privileges to include other custom roles.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=16.6.0<17.1.7 | |
GitLab | >=16.6.0<17.1.7 | |
GitLab | >=17.2.0<17.2.5 | |
GitLab | >=17.2.0<17.2.5 | |
GitLab | >=17.3.0<17.3.2 | |
GitLab | >=17.3.0<17.3.2 |
Upgrade to version 17.1.7, 17.2.5 or 17.3.2
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-8631 is classified as a privilege escalation vulnerability in GitLab EE.
To fix CVE-2024-8631, upgrade GitLab to version 17.1.7, 17.2.5, or 17.3.2 or later.
CVE-2024-8631 affects GitLab EE versions from 16.6 prior to 17.1.7, 17.2 prior to 17.2.5, and 17.3 prior to 17.3.2.
Users assigned the Admin Group Member custom role are specifically impacted by CVE-2024-8631.
There is no official workaround for CVE-2024-8631; updating to a secure version is recommended.