github.com/concourse/dex
View on Github
Activity
- Latest release
- 3mo ago
- Total releases
- 20
- Cadence
- ~41 days
- Last 12 months
- 2
Reach
- Stars
- —
Details
- First release
- Oct 05, 2020
| Version | Released | |
|---|---|---|
v1.14.0
minor
1 CVE
CVE-2020-5415
GHSA-627p-rr78-99rj
BIT-concourse-2020-5415
Dec 20, 2021
GitLab auth uses full name instead of username as user ID, allowing impersonation
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
ImpactInstallations 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 See the GitLab auth docs for details. Concourse installations which do not configure the GitLab auth connector are not affected. PatchesConcourse 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. WorkaroundsGitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team. References
For more informationIf you have any questions or comments about this advisory, you may reach us privately at concourseteam+security@gmail.com. Affected versions
6.4.0
Fixed in
0.0.0-20200730150203-821b48abfd88
6.3.1
6.4.1
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.14.0
minor
Dependencies (37)
+ 29 more |
|
v1.13.0
minor
1 CVE
CVE-2020-5415
GHSA-627p-rr78-99rj
BIT-concourse-2020-5415
Dec 20, 2021
GitLab auth uses full name instead of username as user ID, allowing impersonation
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
ImpactInstallations 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 See the GitLab auth docs for details. Concourse installations which do not configure the GitLab auth connector are not affected. PatchesConcourse 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. WorkaroundsGitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team. References
For more informationIf you have any questions or comments about this advisory, you may reach us privately at concourseteam+security@gmail.com. Affected versions
6.4.0
Fixed in
0.0.0-20200730150203-821b48abfd88
6.3.1
6.4.1
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.13.0
minor
Dependencies (37)
+ 29 more |
|
v1.12.0
minor
1 CVE
CVE-2020-5415
GHSA-627p-rr78-99rj
BIT-concourse-2020-5415
Dec 20, 2021
GitLab auth uses full name instead of username as user ID, allowing impersonation
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
ImpactInstallations 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 See the GitLab auth docs for details. Concourse installations which do not configure the GitLab auth connector are not affected. PatchesConcourse 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. WorkaroundsGitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team. References
For more informationIf you have any questions or comments about this advisory, you may reach us privately at concourseteam+security@gmail.com. Affected versions
6.4.0
Fixed in
0.0.0-20200730150203-821b48abfd88
6.3.1
6.4.1
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.12.0
minor
Dependencies (36)
+ 28 more |
|
v1.11.0
minor
1 CVE
CVE-2020-5415
GHSA-627p-rr78-99rj
BIT-concourse-2020-5415
Dec 20, 2021
GitLab auth uses full name instead of username as user ID, allowing impersonation
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
ImpactInstallations 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 See the GitLab auth docs for details. Concourse installations which do not configure the GitLab auth connector are not affected. PatchesConcourse 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. WorkaroundsGitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team. References
For more informationIf you have any questions or comments about this advisory, you may reach us privately at concourseteam+security@gmail.com. Affected versions
6.4.0
Fixed in
0.0.0-20200730150203-821b48abfd88
6.3.1
6.4.1
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.11.0
minor
Dependencies (36)
+ 28 more |
|
v1.10.0
minor
1 CVE
CVE-2020-5415
GHSA-627p-rr78-99rj
BIT-concourse-2020-5415
Dec 20, 2021
GitLab auth uses full name instead of username as user ID, allowing impersonation
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
ImpactInstallations 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 See the GitLab auth docs for details. Concourse installations which do not configure the GitLab auth connector are not affected. PatchesConcourse 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. WorkaroundsGitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team. References
For more informationIf you have any questions or comments about this advisory, you may reach us privately at concourseteam+security@gmail.com. Affected versions
6.4.0
Fixed in
0.0.0-20200730150203-821b48abfd88
6.3.1
6.4.1
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.10.0
minor
Dependencies (36)
+ 28 more |
|
v1.9.0
minor
1 CVE
CVE-2020-5415
GHSA-627p-rr78-99rj
BIT-concourse-2020-5415
Dec 20, 2021
GitLab auth uses full name instead of username as user ID, allowing impersonation
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
ImpactInstallations 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 See the GitLab auth docs for details. Concourse installations which do not configure the GitLab auth connector are not affected. PatchesConcourse 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. WorkaroundsGitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team. References
For more informationIf you have any questions or comments about this advisory, you may reach us privately at concourseteam+security@gmail.com. Affected versions
6.4.0
Fixed in
0.0.0-20200730150203-821b48abfd88
6.3.1
6.4.1
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.9.0
minor
Dependencies (37)
+ 29 more |
|
v1.8.0
minor
1 CVE
CVE-2020-5415
GHSA-627p-rr78-99rj
BIT-concourse-2020-5415
Dec 20, 2021
GitLab auth uses full name instead of username as user ID, allowing impersonation
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
ImpactInstallations 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 See the GitLab auth docs for details. Concourse installations which do not configure the GitLab auth connector are not affected. PatchesConcourse 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. WorkaroundsGitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team. References
For more informationIf you have any questions or comments about this advisory, you may reach us privately at concourseteam+security@gmail.com. Affected versions
6.4.0
Fixed in
0.0.0-20200730150203-821b48abfd88
6.3.1
6.4.1
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.8.0
minor
Dependencies (36)
+ 28 more |
|
v1.7.0
minor
1 CVE
CVE-2020-5415
GHSA-627p-rr78-99rj
BIT-concourse-2020-5415
Dec 20, 2021
GitLab auth uses full name instead of username as user ID, allowing impersonation
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
ImpactInstallations 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 See the GitLab auth docs for details. Concourse installations which do not configure the GitLab auth connector are not affected. PatchesConcourse 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. WorkaroundsGitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team. References
For more informationIf you have any questions or comments about this advisory, you may reach us privately at concourseteam+security@gmail.com. Affected versions
6.4.0
Fixed in
0.0.0-20200730150203-821b48abfd88
6.3.1
6.4.1
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.7.0
minor
Dependencies (35)
+ 27 more |
|
v1.6.0
minor
1 CVE
CVE-2020-5415
GHSA-627p-rr78-99rj
BIT-concourse-2020-5415
Dec 20, 2021
GitLab auth uses full name instead of username as user ID, allowing impersonation
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
ImpactInstallations 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 See the GitLab auth docs for details. Concourse installations which do not configure the GitLab auth connector are not affected. PatchesConcourse 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. WorkaroundsGitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team. References
For more informationIf you have any questions or comments about this advisory, you may reach us privately at concourseteam+security@gmail.com. Affected versions
6.4.0
Fixed in
0.0.0-20200730150203-821b48abfd88
6.3.1
6.4.1
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.6.0
minor
Dependencies (35)
+ 27 more |
|
v1.5.0
minor
1 CVE
CVE-2020-5415
GHSA-627p-rr78-99rj
BIT-concourse-2020-5415
Dec 20, 2021
GitLab auth uses full name instead of username as user ID, allowing impersonation
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
ImpactInstallations 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 See the GitLab auth docs for details. Concourse installations which do not configure the GitLab auth connector are not affected. PatchesConcourse 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. WorkaroundsGitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team. References
For more informationIf you have any questions or comments about this advisory, you may reach us privately at concourseteam+security@gmail.com. Affected versions
6.4.0
Fixed in
0.0.0-20200730150203-821b48abfd88
6.3.1
6.4.1
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.5.0
minor
Dependencies (34)
+ 26 more |
|
v1.4.0
minor
1 CVE
CVE-2020-5415
GHSA-627p-rr78-99rj
BIT-concourse-2020-5415
Dec 20, 2021
GitLab auth uses full name instead of username as user ID, allowing impersonation
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
ImpactInstallations 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 See the GitLab auth docs for details. Concourse installations which do not configure the GitLab auth connector are not affected. PatchesConcourse 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. WorkaroundsGitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team. References
For more informationIf you have any questions or comments about this advisory, you may reach us privately at concourseteam+security@gmail.com. Affected versions
6.4.0
Fixed in
0.0.0-20200730150203-821b48abfd88
6.3.1
6.4.1
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.4.0
minor
Dependencies (34)
+ 26 more |
|
v1.3.0
minor
1 CVE
CVE-2020-5415
GHSA-627p-rr78-99rj
BIT-concourse-2020-5415
Dec 20, 2021
GitLab auth uses full name instead of username as user ID, allowing impersonation
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
ImpactInstallations 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 See the GitLab auth docs for details. Concourse installations which do not configure the GitLab auth connector are not affected. PatchesConcourse 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. WorkaroundsGitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team. References
For more informationIf you have any questions or comments about this advisory, you may reach us privately at concourseteam+security@gmail.com. Affected versions
6.4.0
Fixed in
0.0.0-20200730150203-821b48abfd88
6.3.1
6.4.1
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.3.0
minor
Dependencies (34)
+ 26 more |
|
v1.2.0
minor
1 CVE
CVE-2020-5415
GHSA-627p-rr78-99rj
BIT-concourse-2020-5415
Dec 20, 2021
GitLab auth uses full name instead of username as user ID, allowing impersonation
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
ImpactInstallations 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 See the GitLab auth docs for details. Concourse installations which do not configure the GitLab auth connector are not affected. PatchesConcourse 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. WorkaroundsGitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team. References
For more informationIf you have any questions or comments about this advisory, you may reach us privately at concourseteam+security@gmail.com. Affected versions
6.4.0
Fixed in
0.0.0-20200730150203-821b48abfd88
6.3.1
6.4.1
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.2.0
minor
Dependencies (34)
+ 26 more |
|
v1.1.0
minor
1 CVE
CVE-2020-5415
GHSA-627p-rr78-99rj
BIT-concourse-2020-5415
Dec 20, 2021
GitLab auth uses full name instead of username as user ID, allowing impersonation
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
ImpactInstallations 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 See the GitLab auth docs for details. Concourse installations which do not configure the GitLab auth connector are not affected. PatchesConcourse 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. WorkaroundsGitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team. References
For more informationIf you have any questions or comments about this advisory, you may reach us privately at concourseteam+security@gmail.com. Affected versions
6.4.0
Fixed in
0.0.0-20200730150203-821b48abfd88
6.3.1
6.4.1
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.1.0
minor
Dependencies (34)
+ 26 more |
|
v0.10.0
minor
1 CVE
CVE-2020-5415
GHSA-627p-rr78-99rj
BIT-concourse-2020-5415
Dec 20, 2021
GitLab auth uses full name instead of username as user ID, allowing impersonation
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
ImpactInstallations 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 See the GitLab auth docs for details. Concourse installations which do not configure the GitLab auth connector are not affected. PatchesConcourse 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. WorkaroundsGitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team. References
For more informationIf you have any questions or comments about this advisory, you may reach us privately at concourseteam+security@gmail.com. Affected versions
6.4.0
Fixed in
0.0.0-20200730150203-821b48abfd88
6.3.1
6.4.1
References Updated Jul 08, 2026 · Source: OSV.dev |
v0.10.0
minor
Dependencies (34)
+ 26 more |
|
v0.9.0
minor
1 CVE
CVE-2020-5415
GHSA-627p-rr78-99rj
BIT-concourse-2020-5415
Dec 20, 2021
GitLab auth uses full name instead of username as user ID, allowing impersonation
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
ImpactInstallations 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 See the GitLab auth docs for details. Concourse installations which do not configure the GitLab auth connector are not affected. PatchesConcourse 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. WorkaroundsGitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team. References
For more informationIf you have any questions or comments about this advisory, you may reach us privately at concourseteam+security@gmail.com. Affected versions
6.4.0
Fixed in
0.0.0-20200730150203-821b48abfd88
6.3.1
6.4.1
References Updated Jul 08, 2026 · Source: OSV.dev |
v0.9.0
minor
Dependencies (34)
+ 26 more |
|
v0.8.0
minor
1 CVE
CVE-2020-5415
GHSA-627p-rr78-99rj
BIT-concourse-2020-5415
Dec 20, 2021
GitLab auth uses full name instead of username as user ID, allowing impersonation
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
ImpactInstallations 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 See the GitLab auth docs for details. Concourse installations which do not configure the GitLab auth connector are not affected. PatchesConcourse 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. WorkaroundsGitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team. References
For more informationIf you have any questions or comments about this advisory, you may reach us privately at concourseteam+security@gmail.com. Affected versions
6.4.0
Fixed in
0.0.0-20200730150203-821b48abfd88
6.3.1
6.4.1
References Updated Jul 08, 2026 · Source: OSV.dev |
v0.8.0
minor
Dependencies (34)
+ 26 more |
|
v0.7.0
minor
1 CVE
CVE-2020-5415
GHSA-627p-rr78-99rj
BIT-concourse-2020-5415
Dec 20, 2021
GitLab auth uses full name instead of username as user ID, allowing impersonation
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
ImpactInstallations 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 See the GitLab auth docs for details. Concourse installations which do not configure the GitLab auth connector are not affected. PatchesConcourse 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. WorkaroundsGitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team. References
For more informationIf you have any questions or comments about this advisory, you may reach us privately at concourseteam+security@gmail.com. Affected versions
6.4.0
Fixed in
0.0.0-20200730150203-821b48abfd88
6.3.1
6.4.1
References Updated Jul 08, 2026 · Source: OSV.dev |
v0.7.0
minor
Dependencies (31)
+ 23 more |
|
v0.6.0
initial
1 CVE
CVE-2020-5415
GHSA-627p-rr78-99rj
BIT-concourse-2020-5415
Dec 20, 2021
GitLab auth uses full name instead of username as user ID, allowing impersonation
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
ImpactInstallations 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 See the GitLab auth docs for details. Concourse installations which do not configure the GitLab auth connector are not affected. PatchesConcourse 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. WorkaroundsGitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team. References
For more informationIf you have any questions or comments about this advisory, you may reach us privately at concourseteam+security@gmail.com. Affected versions
6.4.0
Fixed in
0.0.0-20200730150203-821b48abfd88
6.3.1
6.4.1
References Updated Jul 08, 2026 · Source: OSV.dev |
v0.6.0
initial
Dependencies (31)
+ 23 more |
|
v1.0.0
major
1 CVE
CVE-2020-5415
GHSA-627p-rr78-99rj
BIT-concourse-2020-5415
Dec 20, 2021
GitLab auth uses full name instead of username as user ID, allowing impersonation
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
ImpactInstallations 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 See the GitLab auth docs for details. Concourse installations which do not configure the GitLab auth connector are not affected. PatchesConcourse 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. WorkaroundsGitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team. References
For more informationIf you have any questions or comments about this advisory, you may reach us privately at concourseteam+security@gmail.com. Affected versions
6.4.0
Fixed in
0.0.0-20200730150203-821b48abfd88
6.3.1
6.4.1
References Updated Jul 08, 2026 · Source: OSV.dev |
v1.0.0
major
Dependencies (28)
+ 20 more |