ArgoCD Vulnerable to Use of Risky or Missing Cryptographic Algorithms in Redis Cache
argoproj argo-cd
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-cd/v2 Go |
|
|
argoproj argo-cd
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-cd/v2 Go |
|
|
| github.com/argoproj/argo-cd Go |
| No fix yet |
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. It has been discovered that an unprivileged pod in a different namespace on the same cluster could connect to the Redis server on port 6379. Despite having installed the latest version of the VPC CNI plugin on the EKS cluster, it requires manual enablement through configuration to enforce network policies. This raises concerns that many clients might unknowingly have open access to their Redis servers. This vulnerability could lead to Privilege Escalation to the level of cluster controller, or to information leakage, affecting anyone who does not have strict access controls on their Redis instance. This issue has been patched in version(s) 2.8.19, 2.9.15 and 2.10.10.
From the CVE record · GitHub_M
An unprivileged pod in another namespace on the same cluster can connect to Argo CD's Redis server on port 6379 if Redis access is not strictly controlled. This could expose information or allow privilege escalation to the cluster-controller level. No user interaction is described.
Operators running affected versions of github.com/argoproj/argo-cd/v2 or any version of the unpatched github.com/argoproj/argo-cd Go package should check their Redis access controls.