An issue has been discovered in GitLab CE/EE affecting all versions from 16.1 prior to 16.1.6, 16.2 prior to 16.2.9, 16.3 prior to 16.3.7, 16.4 prior to 16.4.5, 16.5 prior to 16.5.6, 16.6 prior to 16.6.4, and 16.7 prior to 16.7.2 in which user account password reset emails could be delivered to an unverified email address.
The product contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Gitlab | Gitlab | 16.1.0 (including) | 16.1.6 (excluding) |
| Gitlab | Gitlab | 16.2.0 (including) | 16.2.9 (excluding) |
| Gitlab | Gitlab | 16.3.0 (including) | 16.3.7 (excluding) |
| Gitlab | Gitlab | 16.4.0 (including) | 16.4.5 (excluding) |
| Gitlab | Gitlab | 16.5.0 (including) | 16.5.6 (excluding) |
| Gitlab | Gitlab | 16.6.0 (including) | 16.6.4 (excluding) |
| Gitlab | Gitlab | 16.7.0 (including) | 16.7.2 (excluding) |
| Gitlab | Ubuntu | bionic | * |
| Gitlab | Ubuntu | esm-apps/xenial | * |
| Gitlab | Ubuntu | trusty | * |
| Gitlab | Ubuntu | xenial | * |
It is common for an application to have a mechanism that provides a means for a user to gain access to their account in the event they forget their password. Very often the password recovery mechanism is weak, which has the effect of making it more likely that it would be possible for a person other than the legitimate system user to gain access to that user’s account. Weak password recovery schemes completely undermine a strong password authentication scheme. This weakness may be that the security question is too easy to guess or find an answer to (e.g. because the question is too common, or the answers can be found using social media). Or there might be an implementation weakness in the password recovery mechanism code that may for instance trick the system into e-mailing the new password to an e-mail account other than that of the user. There might be no throttling done on the rate of password resets so that a legitimate user can be denied service by an attacker if an attacker tries to recover their password in a rapid succession. The system may send the original password to the user rather than generating a new temporary password. In summary, password recovery functionality, if not carefully designed and implemented can often become the system’s weakest link that can be misused in a way that would allow an attacker to gain unauthorized access to the system.