Vulnerability in github.com/concourse/concourse (CVE-2020-5415)
Summary
Vulnerability in github.com/concourse/concourse (CVE-2020-5415). Confidential information can be exposed externally. Exploitable via users. Mitigation: upgrade to 1.6.1-0.20200730151558-b00d1c8d8576 or later.
Original description
The description as published by the source.
Concourse, versions prior to 6.3.1 and 6.4.1, in installations which use the GitLab auth connector, is vulnerable to identity spoofing by way of configuring a GitLab account with the same full name as another user who is granted access to a Concourse team. GitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2020-5415 has been found in github.com/concourse/concourse.
Attackers can target a specific entry point like users over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade github.com/concourse/concourse to 1.6.1-0.20200730151558-b00d1c8d8576 or later.
If unsure, ask your IT team or search "github.com/concourse/concourse CVE-2020-5415" on the vendor's site.
CVE-2020-5415 (github.com/concourse/concourse) — CWE-290
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: users
Patched: 1.6.1-0.20200730151558-b00d1c8d8576 — apply immediately
Workaround: GitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-290) exists in github.com/concourse/concourse. Attackers reach the vulnerable code path via users without authentication.
Check the vendor advisory for the affected versions of github.com/concourse/concourse. Attack surface: users.
Severity: ?. Confidential information can be exposed externally.
Update to 1.6.1-0.20200730151558-b00d1c8d8576.
Workaround: GitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/concourse/concourse' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/concourse/concourse' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/concourse/concourseを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
GitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team.パッチが適用されるまでの応急処置として、GitLab groups do not have this vulnerability, so GitLab users may be moved into groups which are then configured in the Concourse team. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade github.com/concourse/concourse to 1.6.1-0.20200730151558-b00d1c8d8576ステージング環境で 1.6.1-0.20200730151558-b00d1c8d8576 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory tanzu.vmware.com
- web nvd.nist.gov