Description (CNA)
Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. From version 4.0.0 to before version 4.0.5, the Sync Service's ConfigMap-backed provider (server/sync/sync_cm.go) performs zero authorization checks on all CRUD operations (create, read, update, delete). Any authenticated user — including those using fake Bearer tokens — can create, read, update, and delete Kubernetes ConfigMaps containing synchronization limits. This issue has been patched in version 4.0.5.
Affected (CNA)
| Vendor / product | Versions |
|---|---|
| argoproj / argo-workflows | affected >= 4.0.0, < 4.0.5 |
CWE
CWE-862
References
- https://github.com/argoproj/argo-workflows/security/advisories/GHSA-xchc-cqwg-g76q
- https://github.com/argoproj/argo-workflows/commit/09fff05e0830c14a5e36cc40597ad84881db1ab6
- https://github.com/argoproj/argo-workflows/releases/tag/v4.0.5
ADP enrichment
No English description supplied.
A flaw was found in Argo Workflows. The Sync Service's ConfigMap-backed provider performs zero authorization checks on all create, read, update, and delete operations. This allows any authenticated user, including those using fake Bearer tokens, to manipulate Kubernetes ConfigMaps containing synchronization limits. Such unauthorized access can lead to denial of service or other unauthorized configuration changes within the Kubernetes environment.