Vulnerability in github.com/concourse/concourse (CVE-2022-31683)
Summary
Vulnerability in github.com/concourse/concourse (CVE-2022-31683). Risk of unauthorized operations or information disclosure. Exploitable via FormValue. Mitigation: upgrade to 7.8.3 or later.
Original description
The description as published by the source.
Concourse (7.x.y prior to 7.8.3 and 6.x.y prior to 6.7.9) contains an authorization bypass issue. A Concourse user can send a request with body including :team_name=team2 to bypass team scope check to gain access to certain resources belong to any other 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-2022-31683 has been found in github.com/concourse/concourse.
Attackers can target a specific entry point like FormValue over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/concourse/concourse to 7.8.3 or later.
If unsure, ask your IT team or search "github.com/concourse/concourse CVE-2022-31683" on the vendor's site.
CVE-2022-31683 (github.com/concourse/concourse) — CWE-639
Attack vector: remote (network-reachable) / no user interaction
Attack surface: FormValue
Patched: 7.8.3 — apply immediately
Workaround: No known workarounds for existing versions.
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-639) exists in github.com/concourse/concourse. Attackers reach the vulnerable code path via FormValue.
Check the vendor advisory for the affected versions of github.com/concourse/concourse. Attack surface: FormValue.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 7.8.3.
Workaround: No known workarounds for existing versions.
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
No known workarounds for existing versions.パッチが適用されるまでの応急処置として、No known workarounds for existing versions. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade github.com/concourse/concourse to 7.8.3ステージング環境で 7.8.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com