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.
Path traversal in GitLab Pages leaks other projects' CI artifacts
GitLab CE/EE did not properly validate file paths in GitLab Pages. An authenticated user, under certain conditions and with user interaction, could read private CI/CD job artifacts from other projects. Confidentiality of those artifacts is the impact. Instances on the affected CE/EE ranges are at risk.
What to do: Upgrade GitLab CE/EE to 19.3.9, 19.4.8, or 19.5.6, matching the installed release line.
| Product | Affected | Fixed in |
|---|---|---|
| GitLab CE/EE | all versions from 12.4 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 12.4 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 read private CI/CD job artifacts belonging to other projects through GitLab Pages due to improper validation of file paths.
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