DevOps platform GitLab has reset the passwords of some user accounts, after addressing a critical account takeover vulnerability.
According to the company, in GitLab Community Edition (CE) and Enterprise Edition (EE) versions prior to 14.7.7, 14.8.5, and 14.9.2, a hardcoded password was set when the account was registered using an OmniAuth provider.
The critical-severity bug, which is tracked as CVE-2022-1162 (CVSS score of 9.1), could allow attackers to take over accounts.
In addition to addressing the vulnerability, GitLab reset the passwords for users who it believes might have been impacted by the bug.
“Our investigation shows no indication that users or accounts have been compromised but we’re taking precautionary measures for our users’ security,” the company said.
GitLab has also published a script that allows administrators to identify accounts that might be impacted by CVE-2022-1162. The passwords of all impacted accounts should be reset.
[ READ: Many GitLab Servers Affected by Exploited Flaw Patched 6 Months Ago ]
The latest GitLab release addresses this flaw, along with two high-severity cross-site scripting (XSS) vulnerabilities.
Tracked as CVE-2022-1175 (CVSS score of 8.7), the first of the bugs exists due to improper neutralization of user input in notes. Thus, an attacker could inject HTML in notes and exploit the XSS.
The second high-severity issue is tracked as CVE-2022-1190 (CVSS score of 8.7) and exists because of improper handling of user input. An attacker could exploit the bug by abusing multi-word milestone references in the description of issues or in comments.
GitLab CE/EE versions 14.9.2, 14.8.5, and 14.7.7 address these issues and 14 other medium- and low-severity bugs. All users are advised to upgrade to a current release as soon as possible.
Related: GitKraken Vulnerability Prompts Action From GitHub, GitLab, Bitbucket
Related: GitLab Releases Open Source Tool for Hunting Malicious Code in Dependencies
Related: GitLab Paid Half a Million Dollars in Bug Bounties in One Year