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.
Missing authorization exposes private fork commit comments in GitLab
GitLab CE/EE fails to authorize access to commit comments on a private source fork when they appear in a public project's merge request discussions. An unauthenticated remote attacker can read those comments under those conditions, disclosing limited private discussion content. Instances running the affected 17.11 through 19.5 ranges are affected.
What to do: Upgrade GitLab CE/EE to 19.3.9, 19.4.8, or 19.5.6 for the installed release line. No workaround is stated.
| Product | Affected | Fixed in |
|---|---|---|
| GitLab CE/EE | all versions from 17.11 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 | 19.3.9, 19.4.8, and 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 17.11 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 unauthenticated user to read commit comments from a private source fork through a public project's merge request discussions due to missing authorization checks.
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