GHSA-rc7p-gmvh-xfx2 json
Attack on Kubernetes via Misconfigured Argo Workflows
published 5y ago modified 5y ago
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
### Impact
Users running using the Argo Server with `--auth-mode=server` (which is the default < v3.0.0) AND have exposed their UI to the Internet may allow remote users to execute arbitrary code on their cluster, e.g. crypto-mining.
### Resolution
* Do not expose your user interface to the Internet. * Change configuration. `--auth-mode=client`.
For users using an older 2.x version of Argo Server, consider upgrading to Argo Server version 3.x or later.
Is GHSA-rc7p-gmvh-xfx2 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 FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/argoproj/argo-workflows | all versions |
no fix listed |
References
Sources
- GitHub Advisory GHSA-rc7p-gmvh-xfx2
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.