Information Disclosure in github.com/go-vela/compiler (CVE-2020-26294)
Summary
Vulnerability in github.com/go-vela/compiler (CVE-2020-26294). Confidential information can be exposed externally. Exploitable via env. Mitigation: upgrade to 0.6.1 or later.
Original description
The description as published by the source.
Impact
What kind of vulnerability is it? Who is impacted?
- The ability to expose configuration set in the Vela server via pipeline template functionality.
- It impacts all users of Vela.
Sample of template exposing server configuration using Sprig's env function:
metadata:
template: true
steps:
- name: sample
image: alpine:latest
commands:
# OAuth client ID for Vela <-> GitHub communication
- echo {{ env "VELA_SOURCE_CLIENT" }}
# secret used for server <-> worker communication
- echo {{ env "VELA_SECRET" }}
Patches
Has the problem been patched? What versions should users upgrade to?
- Upgrade to
0.6.1
Additional Recommended Action(s)
- Rotate all secrets
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
- No
For more information
If you have any questions or comments about this advisory:
- Email us at vela@target.com
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-26294 has been found in github.com/go-vela/compiler.
Attackers can target a specific entry point like env over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade github.com/go-vela/compiler to 0.6.1 or later.
If unsure, ask your IT team or search "github.com/go-vela/compiler CVE-2020-26294" on the vendor's site.
CVE-2020-26294 (github.com/go-vela/compiler) — CWE-200
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: env
Patched: 0.6.1 — apply immediately
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.
Information disclosure (CWE-200) exists in github.com/go-vela/compiler. Attackers reach the vulnerable code path via env without authentication.
Check the vendor advisory for the affected versions of github.com/go-vela/compiler. Attack surface: env.
Severity: ?. Confidential information can be exposed externally.
Update to 0.6.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/go-vela/compiler' . 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/go-vela/compiler' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/go-vela/compilerを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/go-vela/compiler to 0.6.1ステージング環境で 0.6.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com
- web github.com
- web pkg.go.dev