CVE-2022-39395 json
Vela Insecure Defaults
published 4y ago modified 4mo ago also GHSA-2w78-ffv6-p46w , GHSA-5m7g-pj8w-7593 , GHSA-xf39-98m2-889v , GO-2022-1100 , EUVD-2022-7245
- cvss
- 9.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 73%
- public exploits
- 0
- none known
Summary
Vela is a Pipeline Automation (CI/CD) framework built on Linux container technology written in Golang. In Vela Server and Vela Worker prior to version 0.16.0 and Vela UI prior to version 0.17.0, some default configurations for Vela allow exploitation and container breakouts. Users should upgrade to Server 0.16.0, Worker 0.16.0, and UI 0.17.0 to fix the issue. After upgrading, Vela administrators will need to explicitly change the default settings to configure Vela as desired. Some of the fixes will interrupt existing workflows and will require Vela administrators to modify default settings. However, not applying the patch (or workarounds) will continue existing risk exposure. Some workarounds are available. Vela administrators can adjust the worker's `VELA_RUNTIME_PRIVILEGED_IMAGES` setting to be explicitly empty, leverage the `VELA_REPO_ALLOWLIST` setting on the server component to restrict access to a list of repositories that are allowed to be enabled, and/or audit enabled repositories and disable pull_requests if they are not needed.
Patch / fix
- go github.com/go-vela/server 0.16.0
- go github.com/go-vela/worker 0.16.0
- go-vela server 0.16.0
- go-vela ui 0.17.0
- go-vela worker 0.16.0
Is CVE-2022-39395 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
1.44% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.6 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 9.9 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| GitHub | 3.1 | 9.9 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/go-vela/server | <0.16.0 |
0.16.0 |
| go | github.com/go-vela/worker | <0.16.0 |
0.16.0 |
Affected products
- go-vela server
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
References
-
github.com
/go-vela/server/commit/05558ee99d70f7d6f83bed7c8f78ac0b35fa26f4
web, patch, third-party-advisory
-
go-vela.github.io
/docs/installation/server/reference/#vela_repo_allowlist
web, vendor-advisory
-
go-vela.github.io
/docs/installation/worker/reference/#vela_runtime_privileged_images
web, vendor-advisory
-
github.com
/go-vela/server/security/advisories/GHSA-5m7g-pj8w-7593
web, third-party-advisory, advisory
-
github.com
/go-vela/ui/security/advisories/GHSA-xf39-98m2-889v
web, third-party-advisory, advisory
-
github.com
/go-vela/worker/security/advisories/GHSA-2w78-ffv6-p46w
web, third-party-advisory, advisory
-
docs.docker.com
/engine/security/#docker-daemon-attack-surface
web, technical-description, third-party-advisory
-
github.com
/go-vela/server/releases/tag/v0.16.0
web, release-notes, third-party-advisory
-
github.com
/go-vela/ui/releases/tag/v0.17.0
web, release-notes, third-party-advisory
-
github.com
/go-vela/worker/releases/tag/v0.16.0
web, release-notes, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-39395
advisory
-
pkg.go.dev
/vuln/GO-2022-1100
web
Sources
- CVE List CVE-2022-39395
- GitHub Advisory GHSA-5m7g-pj8w-7593
- NVD CVE-2022-39395
- OSV GO-2022-1100
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.