argo-cd is vulnerable to unauthenticated DoS attack via malformed Gogs 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. With the default configuration, no webhook.gogs.secret set, Argo CD’s /api/webhook endpoint will crash the entire argocd-server process when it receives a Gogs push event whose JSON field commits[].repo is not set or is null. 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
Under the default configuration, with no webhook.gogs.secret set, a malicious Gogs push event sent to Argo CD’s /api/webhook endpoint can crash the argocd-server process if commits[].repo is missing or null. This denies service to legitimate clients; the input does not specify whether authentication is required.
Engineers running Argo CD 1.2.0–1.8.7, 2.0.0-rc1–2.14.19, or affected 3.x releases before 3.0.19, 3.1.8, or 3.2.0-rc2 should check their deployments.