First published: Wed May 11 2022(Updated: )
An issue has been discovered in GitLab affecting all versions starting from 12.6 before 14.8.6, all versions starting from 14.9 before 14.9.4, all versions starting from 14.10 before 14.10.1. GitLab was not correctly authenticating a user that had some certain amount of information which allowed an user to authenticate without a personal access token.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=12.6.0<14.8.6 | |
GitLab | >=12.6.0<14.8.6 | |
GitLab | >=14.9.0<14.9.4 | |
GitLab | >=14.9.0<14.9.4 | |
GitLab | =14.10.0 | |
GitLab | =14.10.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-1426 is rated as a high severity vulnerability due to its impact on user authentication.
To remediate CVE-2022-1426, upgrade GitLab to version 14.8.6 or later, or 14.9.4 or later, or 14.10.1 or later.
CVE-2022-1426 affects GitLab versions from 12.6 before 14.8.6, 14.9 before 14.9.4, and 14.10 before 14.10.1.
All users of GitLab versions specified in the vulnerability are impacted if they are running affected versions.
Yes, you can verify your installed GitLab version through the application interface or command line to see if it's vulnerable.