| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/concourse/concourse | ≥ 0.0.0, < 1.6.1-0.20200730151558-b00d1c8d8576≥ 1.6.1, < 6.3.1≥ 6.4.0, < 6.4.1< 0.0.0-20200730151558-b00d1c8d8576 | 1.6.1-0.20200730151558-b00d1c8d85766.3.16.4.10.0.0-20200730151558-b00d1c8d8576 |
| github.com/concourse/dex | ≥ 0.0.0, < 6.3.1≥ 6.4.0, < 6.4.1< 0.0.0-20200730150203-821b48abfd88 | 6.3.16.4.10.0.0-20200730150203-821b48abfd88 |
| concourse | ≥ 6.4.0, < 6.4.1< 6.3.1 | 6.4.16.3.1 |
Installations which use the GitLab auth connector are vulnerable to identity spoofing by way of configuring a GitLab account with the same full name as another GitLab user who is granted access to a Concourse team by having their full name listed under users in the team configuration or given to the --gitlab-user flag.
See the GitLab auth docs for details.
Concourse installations which do not configure the GitLab auth connector are not affected.
Concourse v6.3.1 and v6.4.1 were both released with a fix on August 4th, 2020.
Both versions change the GitLab connector to use the username, rather than the full name. This was always the intent, and the previous behavior was originally reported as a bug (concourse/dex#7) prior to being reported as a security issue.
Any Concourse teams which configure GitLab users will have to switch each user from their full name to their username upon upgrading to these versions.
GitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team.
If you have any questions or comments about this advisory, you may reach us privately at [email protected].
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free