[ad_1]
Researchers have disclosed particulars of a brand new safety vulnerability in GitLab, an open-source DevOps software program, that might doubtlessly enable a distant, unauthenticated attacker to get better user-related info.
Tracked as CVE-2021-4191 (CVSS rating: 5.3), the medium-severity flaw impacts all variations of GitLab Group Version and Enterprise Version ranging from 13.0 and all variations ranging from 14.4 and previous to 14.8.
Credited with discovering and reporting the flaw is Jake Baines, a senior safety researcher at Rapid7. Following accountable disclosure on November 18, 2021, patches had been launched for self-managed servers as a part of GitLab essential safety releases 14.8.2, 14.7.4, and 14.6.5 shipped on February 25, 2022.
“The vulnerability is the results of a lacking authentication verify when executing sure GitLab GraphQL API queries,” Baines mentioned in a report printed Thursday. “A distant, unauthenticated attacker can use this vulnerability to gather registered GitLab usernames, names, and electronic mail addresses.”
Profitable exploitation of the API info leak might allow malicious actors to enumerate and compile lists of legit usernames belonging to a goal that may then be utilized as a stepping stone to conduct brute-force assaults, together with password guessing, password spraying, and credential stuffing.
“The knowledge leak additionally doubtlessly permits an attacker to create a brand new username wordlist based mostly on GitLab installations — not simply from gitlab.com [which is patched as of writing] but in addition from the opposite 50,000 GitLab situations that may be reached from the web,” Baines mentioned.
In addition to CVE-2021-4191, the patch additionally addresses six different safety flaws, one in every of which is a essential situation (CVE-2022-0735, CVSS rating: 9.6) that permits an unauthorized attacker to siphon the runner registration tokens used to authenticate and authorize CI/CD jobs hosted on GitLab situations.
[ad_2]
