{"uuid": "d806dbc4-a5c1-4c41-bc55-f2af93f04216", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45409", "type": "seen", "source": "https://t.me/IntrusionExploit/310", "content": "\ud83d\udd12 GitLab releases security updates to fix a critical SAML authentication vulnerability affecting self-managed installations of GitLab Community Edition (CE) and Enterprise Edition (EE).\n\ud83d\uded1 Vulnerability: CVE-2024-45409\nThe vulnerability resides in the OmniAuth-SAML and Ruby-SAML libraries. An attacker can craft a malicious SAML response to bypass authentication, causing GitLab to mistake them for an authenticated user.\n\ud83d\udcc5 Affected versions:\nGitLab 17.3.3, 17.2.7, 17.1.8, 17.0.8, 16.11.10, and all earlier versions.\n\u2705 Solution:\nUpdate to GitLab versions 17.3.3, 17.2.7, 17.1.8, 17.0.8, or 16.11.10, where OmniAuth SAML has been upgraded to version 2.2.1 and Ruby-SAML to 1.17.0.\n\nNote: Users on GitLab.com do not need to take any action as this issue only affects self-managed installations.\n\nIf you cannot upgrade now, enable two-factor authentication (2FA) for all accounts and set the SAML 2FA bypass option to \"disable.\"\n\n\ud83d\udc49 Make sure your system is secure!", "creation_timestamp": "2024-09-23T17:23:00.000000Z"}