First published: Tue Oct 05 2021(Updated: )
In all versions of GitLab CE/EE since version 14.1, an improper access control vulnerability allows users with expired password to still access GitLab through git and API through access tokens acquired before password expiration.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=14.1.0<14.1.7 | |
GitLab | >=14.1.0<14.1.7 | |
GitLab | >=14.2.0<14.2.5 | |
GitLab | >=14.2.0<14.2.5 | |
GitLab | =4.3.0 | |
GitLab | =4.3.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-39872 is classified as a high severity vulnerability due to improper access control allowing expired users to access GitLab via access tokens.
To mitigate CVE-2021-39872, users should upgrade to GitLab versions 14.1.8, 14.2.6, or later where this vulnerability is patched.
CVE-2021-39872 affects all versions of GitLab CE/EE starting from 14.1.0 up to and including 14.1.7 and 14.2.0 up to and including 14.2.5.
Users with expired passwords are impacted by CVE-2021-39872, as they can still access GitLab through git and API using previously acquired access tokens.
Currently, the recommended solution for CVE-2021-39872 is to upgrade to a patched version of GitLab, as there are no effective workarounds available.