CVE-2024-1211: 
GitLab vulnerability analysis and mitigation

An issue has been discovered in GitLab CE/EE affecting all versions starting from 10.6 prior to 16.9.7, starting from 16.10 prior to 16.10.5, and starting from 16.11 prior to 16.11.2 in which cross-site request forgery may have been possible on GitLab instances configured to use JWT as an OmniAuth provider (GitLab Release, CVE Mitre).

The vulnerability has been assigned a CVSS score of 6.4 (Medium severity) with the following vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N. The issue specifically relates to the JWT OmniAuth provider configuration in GitLab instances, where cross-site request forgery attacks could potentially be executed (GitLab Release).

If successfully exploited, this vulnerability could allow attackers to perform cross-site request forgery attacks against GitLab instances that use JWT as an OmniAuth provider, potentially compromising user authentication and authorization mechanisms (GitLab Release).

The vulnerability has been fixed in GitLab versions 16.9.7, 16.10.5, and 16.11.2. Users are strongly recommended to upgrade their GitLab installations to one of these patched versions immediately. GitLab.com is already running the patched version (GitLab Release).

The vulnerability was responsibly disclosed through GitLab's HackerOne bug bounty program by security researcher sim4n6, demonstrating the effectiveness of GitLab's security response program (GitLab Release).