First published: Mon Oct 04 2021(Updated: )
In all versions of GitLab CE/EE, an attacker with physical access to a user’s machine may brute force the user’s password via the change password function. There is a rate limit in place, but the attack may still be conducted by stealing the session id from the physical compromise of the account and splitting the attack over several IP addresses and passing in the compromised session value from these various locations.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=1.0.0<14.1.7 | |
GitLab | >=1.0.0<14.1.7 | |
GitLab | >=14.2<14.2.5 | |
GitLab | >=14.2<14.2.5 | |
GitLab | >=14.3<14.3.1 | |
GitLab | >=14.3<14.3.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-39899 is considered a medium severity vulnerability due to its potential for unauthorized access if an attacker has physical access to a user's machine.
To mitigate CVE-2021-39899, ensure that your GitLab installation is updated to version 14.1.8 or higher, or to versions 14.2.6 and 14.3.2 or higher.
CVE-2021-39899 affects all versions of GitLab CE/EE prior to the patched versions, allowing physical access attackers to potentially brute force user passwords.
CVE-2021-39899 allows an attacker with physical access to a user’s machine to potentially change passwords through brute force, compromising account security.
While no specific workaround exists, limiting physical access to machines and educating users on password security can help mitigate risks associated with CVE-2021-39899.