First published: Tue Jan 18 2022(Updated: )
An issue has been discovered in GitLab affecting all versions starting from 7.7 before 14.4.5, all versions starting from 14.5.0 before 14.5.3, all versions starting from 14.6.0 before 14.6.2. GitLab was vulnerable to a Cross-Site Request Forgery attack that allows a malicious user to have their GitHub project imported on another GitLab user account.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=7.7<14.4.5 | |
GitLab | >=7.7<14.4.5 | |
GitLab | >=14.5.0<14.5.3 | |
GitLab | >=14.5.0<14.5.3 | |
GitLab | >=14.6.0<14.6.2 | |
GitLab | >=14.6.0<14.6.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-0154 has been classified as a medium severity vulnerability due to the potential for Cross-Site Request Forgery attacks.
To fix CVE-2022-0154, users should upgrade to GitLab versions 14.4.5 or later, 14.5.3 or later, or 14.6.2 or later.
CVE-2022-0154 enables Cross-Site Request Forgery attacks that could allow malicious users to execute unauthorized commands in the GitLab application.
CVE-2022-0154 affects all GitLab versions from 7.7 up to 14.4.5, 14.5.0 up to 14.5.3, and 14.6.0 up to 14.6.2.
Yes, CVE-2022-0154 is applicable to both community and enterprise versions of GitLab.