Unauthenticated argocd-server panic via a malicious Bitbucket-Server webhook payload
argoproj argo-cd
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-cd Go |
| No fix yet |
| github.com/argoproj/argo-cd/v2 Go |
|
|
argoproj argo-cd
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-cd Go |
| No fix yet |
| github.com/argoproj/argo-cd/v2 Go |
|
|
| github.com/argoproj/argo-cd/v3 Go |
|
|
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Versions 1.2.0 through 1.8.7, 2.0.0-rc1 through 2.14.19, 3.0.0-rc1 through 3.2.0-rc1, 3.1.7 and 3.0.18 are vulnerable to malicious API requests which can crash the API server and cause denial of service to legitimate clients. Without a configured webhook.bitbucketserver.secret, Argo CD's /api/webhook endpoint crashes when receiving a malformed Bitbucket Server payload (non-array repository.links.clone field). A single unauthenticated request triggers CrashLoopBackOff, and targeting all replicas causes complete API outage. This issue is fixed in versions 2.14.20, 3.2.0-rc2, 3.1.8 and 3.0.19.
From the CVE record · GitHub_M
Argo CD's /api/webhook endpoint can crash the API server when it receives a malformed Bitbucket Server payload and webhook.bitbucketserver.secret is not configured. A single unauthenticated request can trigger CrashLoopBackOff; requests targeting all replicas can cause a complete API outage.
Teams running affected Argo CD versions 1.2.0–1.8.7, 2.0.0-rc1 through versions before 2.14.20, or affected 3.x releases before 3.0.19, 3.1.8, or 3.2.0-rc2 should check their deployments.