GitLab patches 37 flaws in 19.5.6, 19.4.8 and 19.3.9
Four issues are high severity, including stored XSS and a CI/CD race that can expose protected variables.
Race condition exposes protected CI/CD variables in GitLab
A race condition in GitLab CE/EE pipeline job authorization can, under certain conditions, let an authenticated user access protected CI/CD variables and resources. The attacker must already have an account; no user interaction is required, but the race is difficult to win. Confidentiality and integrity of those protected resources are at risk. All CE/EE releases from 9.3 through the listed fixed versions are affected.
What to do: Upgrade GitLab CE/EE to 19.3.9, 19.4.8, or 19.5.6. GitLab has not named a workaround.
| Product | Affected | Fixed in |
|---|---|---|
| GitLab CE/EE | 9.3 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 | 19.3.9, 19.4.8, 19.5.6 |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 9.3 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user to access protected CI/CD variables and resources due to a race condition in pipeline job authorization.
Four issues are high severity, including stored XSS and a CI/CD race that can expose protected variables.
Today 1.1K readers · 1.3K views · 176 reads · all time 202K views