GitLab customers are being warned of a critical safety vulnerability affecting variations of GitLab Enterprise Version (EE) previous to 17.4.2, 17.3.5, and 17.2.9 — which, if left unpatched, permits for steady integration (CI) pipeline triggers that might enable for distant code execution.
“A difficulty was found in GitLab EE affecting all variations ranging from 12.5 previous to 17.2.9, ranging from 17.3, previous to 17.3.5, and ranging from 17.4 previous to 17.4.2, which permits working pipelines on arbitrary branches,” the corporate explains in its announcement of the bug. “This can be a vital severity concern (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N, 9.6).”
A vulnerability in GitLab Enterprise Version exposes the potential for arbitrary code execution in CI/CD pipelines, and desires patching pronto. (📷: GitLab)
Left unchecked, the vulnerability — reported to the corporate via the HackerOne bug bounty program — permits attackers to run steady integration (CI) and steady deployment (CD) pipelines on the branches of their selection. This, in flip, can enable for arbitrary code execution if department safety measures are bypassed, that means patching instantly is strongly really useful.
The identical new releases deliver a repair for a associated concern that permits an attacker to set off pipelines as an arbitrary different person, rated excessive severity and affecting each the Enterprise Version and the Neighborhood Version of the GitLab software program. Different fixes shut a server-side request forgery (SSRF) vulnerability in GitLab EE’s analytics dashboard, a degradation of service concern with diff viewing, a cross-site scripting downside within the software program’s OAuth web page, and a hadful of different bugs.
Full particulars on the vulnerabilities, which don’t have an effect on these internet hosting their software program on GitLab.com nor these utilizing the GitLab Devoted service, can be found on the GitLab web site.