Workflow re-write vulnerability using input parameter
### Impact * Allow end-users to set input parameters, but otherwise expect workflows to be secure. ### Patches Not yet. ### Workarounds * Set `EXPRESSION_TEMPLATES=false` for the workflow controller ### References * https://github.com/argoproj/argo-workflows/issues/6441 ### For more information If you have any questions or comments about this advisory: * Open an issue in [example link to repo](http://example.com) * Email us at [example email address](mailto:example@example.com)
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2021-37914US | medium6.5 | — | ||
In Argo Workflows through 3.1.3, if EXPRESSION_TEMPLATES is enabled and untrusted users are allowed to specify input parameters when running workflows, an attacker may be able to d… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/argoproj/argo-workflows/commit/2a2ecc916925642fd8cb1efd026588e6828f82e1WEB
- https://github.com/argoproj/argo-workflows/issues/6441WEB
- https://github.com/argoproj/argo-workflows/pull/6285WEB
- https://github.com/argoproj/argo-workflows/pull/6442WEB
- https://github.com/argoproj/argo-workflows/security/advisories/GHSA-h563-xh25-x54qWEB
- https://nvd.nist.gov/vuln/detail/CVE-2021-37914ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan