Critical · published February 16, 2023
🚨 An improper authorization flaw in Argo CD lets users with limited access update ANY cluster secret! 🔥 Think of it like a restaurant where the waitstaff can access the entire kitchen without checking in with the chef — if they can change any ingredient, they might serve up something unexpected or even harmful! This vulnerability could allow an attacker to escalate their privileges, potentially seizing control over Kubernetes resources or crippling the Argo CD functionality by severing connections to vital external clusters. The consequences could be absolutely devastating, leading to a breakdown or misuse of your deployment pipelines!
Think of it like a restaurant where the waitstaff can access the entire kitchen without checking in with the chef — if they can change any ingredient, they might serve up something unexpected or even harmful! Argo CD versions from 2.3.0-rc1 up to 2.3.17, 2.4.23, 2.5.11, and 2.6.2 have a flaw where users authorized to update at least one cluster secret can manipulate any secret, bypassing intended authorization checks.
This vulnerability could allow an attacker to escalate their privileges, potentially seizing control over Kubernetes resources or crippling the Argo CD functionality by severing connections to vital external clusters. The consequences could be absolutely devastating, leading to a breakdown or misuse of your deployment pipelines! Immediately upgrade to Argo CD versions 2.6.2, 2.5.11, 2.4.23, or 2.3.17 to fix this critical bug. Alternatively, you can modify your RBAC settings to completely revoke `clusters, update` access, or use the `destinations` and `clusterResourceWhitelist` fields to restrict updates more effectively. Don't delay! You've got this! Secure your clusters and let your security hero status shine! 🛡️