CVE-2020-5415: Open Source Vulnerability in Concourse

concourse Updated 02 Oct 2025

Summary

06/03/2024
Yes i
Critical
Not published

CVE-2020-5415: Concourse's GitLab auth allows impersonation. Affects concourse across 2 version ranges.

< 6.3.1 >= 6.4.0, < 6.4.1

Fixed in 6.3.1 or 6.4.1, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2020-5415 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Concourse is an open-source continuous integration and delivery (CI/CD) platform that helps automate software build, test, and deployment processes. It is widely used for managing pipelines and workflows in various development environments. However, versions prior to 6.3.1 and 6.4.1 of Concourse, specifically those installations utilizing the GitLab auth connector, are susceptible to an identity spoofing vulnerability. This vulnerability arises when a GitLab account is configured with the same full name as another user who has been granted access to a Concourse team. It is important to note that GitLab groups are not affected by this vulnerability, and users can be moved into groups and then configured within the Concourse team to mitigate the risk.

Vulnerability Detail

The identified vulnerability in Concourse allows for identity spoofing, potentially leading to unauthorized access and privilege escalation. By exploiting this vulnerability, an attacker can create a GitLab account with the same full name as another user who has legitimate access to a Concourse team. This impersonation can result in unauthorized actions being performed within the affected Concourse environment. It is crucial to address this vulnerability promptly to prevent potential security breaches and maintain the integrity of the CI/CD processes.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 6.3.1 6.3.1
  • >= 6.4.0, < 6.4.1 6.4.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Conclusion

The identified vulnerability in Concourse poses a significant risk of identity spoofing, potentially leading to unauthorized access and privilege escalation. It is crucial to update Concourse to the recommended versions and review GitLab account configurations to mitigate the risk. For further assistance and support in addressing this vulnerability, please contact DevNack.com.

See every vulnerability recorded for concourse →

Share this vulnerability

FAQ

Concourse is an open-source CI/CD platform used for automating software build, test, and deployment processes.

Versions prior to 6.3.1 and 6.4.1 of Concourse are vulnerable to identity spoofing when using the GitLab auth connector.

No, GitLab groups are not vulnerable to this identity spoofing issue. Users can be moved into groups and then configured within the Concourse team to mitigate the risk.

The vulnerability can lead to unauthorized access and privilege escalation within the affected Concourse environment, potentially compromising the integrity of CI/CD processes.

To fix this vulnerability, update Concourse to version 6.3.1 or 6.4.1 and review GitLab account configurations to minimize the risk of identity spoofing.

Related vulnerabilities

Recent vulnerabilities recorded for concourse.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 6.3.1 6.3.1
  • >= 6.4.0, < 6.4.1 6.4.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback