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.
Authz flaw in GitLab workspaces leaks other namespaces' Kubernetes secrets
GitLab CE/EE mishandles authorization in workspaces, so under certain conditions an authenticated user can read Kubernetes Secrets from other namespaces. The attacker needs a high-privilege account and a cluster already connected through the GitLab agent for Kubernetes; no user interaction is required. Impact is mainly disclosure of those secrets, with limited integrity effect. Instances on the affected 17.6 through 19.5 ranges that use this agent are affected.
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 | 17.6 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.6 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 Kubernetes Secrets from other namespaces in clusters connected through the GitLab agent for Kubernetes due to incorrect authorization in workspaces.
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