CVE-2021-37914: Workflow re-write vulnerability in github.com/argoproj/argo-workflows
Summary
CVE-2021-37914: Workflow re-write vulnerability using input parameter in github.com/argoproj/argo-workflows. Affected versions are not published. No fix is published. How to fix ↓
Also tracked for
- argo-workflows · Bitnami
- github.com/argoproj/argo-workflows/v3 · Go
The same CVE-2021-37914 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The package under scrutiny is github.com/argoproj/argo-workflows, which is written in Go. It is a workflow engine that allows users to define, run, and manage complex workflows. It provides a declarative way to define workflows using YAML or JSON files. The package is widely used in various applications and systems.
Vulnerability Detail
The vulnerability, identified as CVE-2021-37914, is a workflow re-write vulnerability that can be exploited using an input parameter in github.com/argoproj/argo-workflows. This vulnerability allows an attacker to modify the workflow by manipulating the input parameter, potentially leading to unauthorized access, data leakage, or code execution. The vulnerability affects versions 0 and above of github.com/argoproj/argo-workflows, as well as versions 3.1.0 to 3.1.6 of github.com/argoproj/argo-workflows/v3.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
There is currently no known workaround for this vulnerability. It is recommended to apply the fix mentioned above.
Conclusion
In conclusion, the workflow re-write vulnerability in github.com/argoproj/argo-workflows can allow an attacker to modify workflows and potentially gain unauthorized access or execute malicious code. It is crucial to update to the latest version of the package to mitigate this vulnerability.
See every vulnerability recorded for github.com/argoproj/argo-workflows →
FAQ
This vulnerability allows an attacker to modify workflows, potentially leading to unauthorized access, data leakage, or code execution.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply upload your Gopkg.lock file and Vulert will analyze it for vulnerabilities in real-time.
Yes, versions 0 and above of github.com/argoproj/argo-workflows are affected. Additionally, versions 3.1.0 to 3.1.6 of github.com/argoproj/argo-workflows/v3 are also vulnerable.
Yes, it is recommended to update to the latest version of github.com/argoproj/argo-workflows. For versions 0 and above, upgrading to a fixed version is necessary. For versions 3.1.0 to 3.1.6 of github.com/argoproj/argo-workflows/v3, upgrading to version 3.1.7 or later is required.
Yes, this vulnerability can be exploited remotely if the affected package is exposed to the internet.
Related vulnerabilities
Recent vulnerabilities recorded for github.com/argoproj/argo-workflows.
