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.
Maven cache tampering in GitLab EE virtual registry
GitLab EE virtual registries can accept a malformed response and store it as a cached Maven package. An unauthenticated attacker who controls an upstream repository can, under certain conditions, change cached packages that belong to other repositories in the same virtual registry. Integrity of those packages is affected; confidentiality and availability are not. GitLab Enterprise Edition installations using this virtual-registry feature are affected.
What to do: Upgrade GitLab EE to 19.3.9, 19.4.8, or 19.5.6, matching the installed release line.
| Product | Affected | Fixed in |
|---|---|---|
| GitLab EE | 18.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 EE affecting all versions from 18.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 individual controlling an upstream repository to alter cached Maven packages from other repositories in the same virtual registry due to improper response validation.
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