Argo CD is Vulnerable to Unauthenticated Remote DoS via malformed Azure DevOps git.push webhook
argoproj argo-cd
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-cd/v2 Go |
|
|
| github.com/argoproj/argo-cd/v3 Go |
|
argoproj argo-cd
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-cd/v2 Go |
|
|
| github.com/argoproj/argo-cd/v3 Go |
|
3.2.0-rc23.1.83.0.19| github.com/argoproj/argo-cd Go |
| No fix yet |
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. For versions 2.9.0-rc1 through 2.14.19, 3.0.0-rc1 through 3.2.0-rc1, 3.1.6 and 3.0.17, when the webhook.azuredevops.username and webhook.azuredevops.password are not set in the default configuration, the /api/webhook endpoint crashes the entire argocd-server process when it receives an Azure DevOps Push event whose JSON array resource.refUpdates is empty. The slice index [0] is accessed without a length check, causing an index-out-of-range panic. A single unauthenticated HTTP POST is enough to kill the process. This issue is resolved 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 Azure DevOps webhook can crash the entire argocd-server process when it receives a Push event with an empty resource.refUpdates array. If the Azure DevOps webhook username and password are unset, a single unauthenticated HTTP POST can trigger the crash; no user interaction is required.
Operators using affected github.com/argoproj/argo-cd/v2 or /v3 versions should check their deployments; the unversioned github.com/argoproj/argo-cd package is listed as affected in all versions with no fix.