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.
Scope bypass in GitLab Kubernetes agent proxy
GitLab CE/EE did not enforce granular personal-access-token scopes in the Kubernetes agent proxy-user authorization flow. An authenticated user who already holds a limited-scope token can, under certain conditions, authorize Kubernetes API proxy access beyond that token's intended boundaries, with limited confidentiality and integrity impact. GitLab CE/EE 19.2 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 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.
| Product | Affected | Fixed in |
|---|---|---|
| GitLab CE/EE | 19.2 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 19.2 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 holding a granular personal access token with limited scope to authorize Kubernetes API proxy access beyond the token's intended boundaries due to missing granular scope enforcement in the Kubernetes agent proxy-user authorization flow.
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