CVE-2024-6385: 
GitLab vulnerability analysis and mitigation

A critical vulnerability (CVE-2024-6385) was discovered in GitLab CE/EE affecting versions starting from 15.8 prior to 16.11.6, from 17.0 prior to 17.0.4, and from 17.1 prior to 17.1.2. The vulnerability allows an attacker to trigger a pipeline as another user under certain circumstances (GitLab Release, Arctic Wolf).

The vulnerability has been assigned a critical severity rating with a CVSS v3.1 base score of 9.6 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N). The vulnerability is characterized as a low-complexity exploit that can be executed remotely. It specifically affects GitLab's pipeline functionality, which is a collection of automated processes that run in stages to build, test, and deploy code (Hacker News).

The vulnerability allows attackers to execute pipeline jobs as arbitrary users, potentially leading to unauthorized access to private repositories and CI/CD variables. This could result in the ability to trigger CI/CD pipelines and control deployments, environments, and packages. Additionally, through the exploitation of CI_JOB_TOKEN, attackers might gain access to private information such as lists of groups, projects, issues, and merge requests (Arctic Wolf).

GitLab has released patches to address this vulnerability. Organizations are strongly recommended to upgrade to the following fixed versions: GitLab CE/EE version 16.11.6 (for 15.8-16.11 users), version 17.0.4 (for 17.0 users), or version 17.1.2 (for 17.1 users). GitLab.com and GitLab Dedicated instances are already running the patched version (GitLab Release).