GitLab Patches Critical SAML Authentication Bypass in Self-Managed Instances
Vulnerability Disclosure · 3 sources · Updated 4mo ago · First seen Sep 15, 2024

GitLab released emergency security updates across multiple CE and EE versions to fix CVE-2024-45409, a critical SAML authentication bypass affecting self-managed instances configured for SAML-based sign-in. The company said the issue was mitigated by updating omniauth-saml to 2.2.1 and ruby-saml to 1.17.0, and urged administrators to upgrade immediately to patched releases spanning the 17.x and 16.x branches. GitLab.com and GitLab Dedicated were already remediated and were not exposed in the same way.
GitLab also published mitigation and threat-hunting guidance for organizations that could not patch immediately, including enforcing GitLab two-factor authentication for all users and disabling the SAML two-factor bypass option. To help defenders identify attempted or successful exploitation, the advisories pointed to review of application_json and auth_json logs and shared Sigma-style detection ideas focused on anomalous extern_uid values and suspicious IP mismatches during authentication events.


