GHSA-6c73-2v8x-qpvm
Suggest an improvement- Source
- https://github.com/advisories/GHSA-6c73-2v8x-qpvm
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2021/08/GHSA-6c73-2v8x-qpvm/GHSA-6c73-2v8x-qpvm.json
- JSON Data
- https://api.osv.dev/v1/vulns/GHSA-6c73-2v8x-qpvm
- Aliases
- Published
- 2021-08-23T19:41:30Z
- Modified
- 2024-08-21T14:57:06.425333Z
- Summary
- Argo Server TLS requests could be forged by attacker with network access
- Details
-
Impact
We are not aware of any exploits. This is a pro-active fix.
Impacted:
- You are running Argo Server < v3.0 with
--secure=trueor >= v3.0 with--secureunspecified (note - running in secure mode is recommended regardless). - The attacker is within your network. If you expose Argo Server to the Internet then "your network" is "the Internet".
The Argo Server's keys are packaged within the image. They could be extracted and used to decrypt traffic, or forge requests.
Patches
https://github.com/argoproj/argo-workflows/pull/6540
Workarounds
- Make sure that your Argo Server service or pod are not directly accessible outside of your cluster. Put TLS load balancer in front of it.
This was identified by engineers at Jetstack.io
- You are running Argo Server < v3.0 with
- Database specific
{ "nvd_published_at": null, "cwe_ids": [], "severity": "MODERATE", "github_reviewed": true, "github_reviewed_at": "2021-08-23T17:02:24Z" }- References
Affected packages
Go / github.com/argoproj/argo-workflows/v3
Package
- Name
- github.com/argoproj/argo-workflows/v3
- View open source insights on deps.dev
- Purl
- pkg:golang/github.com/argoproj/argo-workflows/v3
Go / github.com/argoproj/argo-workflows/v3
Package
- Name
- github.com/argoproj/argo-workflows/v3
- View open source insights on deps.dev
- Purl
- pkg:golang/github.com/argoproj/argo-workflows/v3