GHSA-f9gq-prrc-hrhc Unauthenticated argocd-server panic via a malicious Bitbucket-Server webhook payload

• Go github.com/argoproj/argo-cd: >= 1.2.0, <= 1.8.7 (no fix yet) • Go github.com/argoproj/argo-cd/v2: >= 2.0.0-rc1, < 2.14.20 → fixed in 2.14.20 • Go github.com/argoproj/argo-cd/v3: >= 3.2.0-rc1, < 3.2.0-rc2 → fixed in 3.2.0-rc2 • Go github.com/argoproj/argo-cd/v3: >= 3.1.0-rc1, < 3.1.8 → fixed in 3.1.8 • Go github.com/argoproj/argo-cd/v3: >= 3.0.0-rc1, < 3.0.19 → fixed in 3.0.19

Summary Unpatched Argo CD versions are vulnerable to malicious API requests which can crash the API server and cause denial of service to legitimate clients. With the default configuration, no `webhook.bitbucketserver.secret` set, Argo CD’s /api/webhook endpoint will crash the entire argocd-server process when it receives a Bitbucket-Server push event whose JSON field `repository.links.clone` is anything other than an array. A single unauthenticated curl request can push the control-plane into CrashLoopBackOff; repeating the request on each replica causes a complete outage of the API. Details ```go // webhook.go (Bitbucket-Server branch in affectedRevisionInfo) for _, l := range payload.Repository.Links["clone"].([]any) { // ``` For more information • Open an issue in the Argo CD issue tracker or discussions • Join us on Slack in channel #argo-cd Credits Discovered by Jakub Ciolek at AlphaSense.