Critical · published June 6, 2022
🚨 A sneaky flaw allows attackers to hijack accounts on GitLab EE by exploiting the SCIM feature — and it affects a range of versions! 🔥 Think of it like a party where the host allows anyone with the right invite to change guests' names and take over their RSVP — chaos ensues when someone gets access to the guest list! With this vulnerability, an attacker can gain access to a targeted account just by changing the email address to one they control. Once in, they could change the password, lock out the rightful owner, and wreak havoc on sensitive data or resources. The lack of two-factor authentication means this takeover could be alarmingly easy!
Think of it like a party where the host allows anyone with the right invite to change guests' names and take over their RSVP — chaos ensues when someone gets access to the guest list! This account takeover vulnerability arises when group SAML SSO is configured in GitLab EE, allowing Premium group owners to invite users and modify their details via SCIM without proper restrictions.
With this vulnerability, an attacker can gain access to a targeted account just by changing the email address to one they control. Once in, they could change the password, lock out the rightful owner, and wreak havoc on sensitive data or resources. The lack of two-factor authentication means this takeover could be alarmingly easy! To protect against this, immediately update your GitLab EE to the fixed versions: 14.9.5, 14.10.4, or 15.0.1. Additionally, enforce two-factor authentication for all accounts to add an extra layer of security against unwanted access. Regularly review user permissions and group settings as a best practice! You've got this! Follow these steps, and you’ll keep your GitLab environment secure and sound! 🛡️