Repository Credentials Race Condition Crashes Argo CD Server
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. Versions between 2.1.0 and 2.14.19, 3.2.0-rc1, 3.1.0-rc1 through 3.1.7, and 3.0.0-rc1 through 3.0.18 contain a race condition in the repository credentials handler that can cause the Argo CD server to panic and crash when concurrent operations are performed on the same repository URL. The vulnerability is located in numerous repository related handlers in the util/db/repository_secrets.go file. A valid API token with repositories resource permissions (create, update, or delete actions) is required to trigger the race condition. This vulnerability causes the entire Argo CD server to crash and become unavailable. Attackers can repeatedly and continuously trigger the race condition to maintain a denial-of-service state, disrupting all GitOps operations. 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
A race condition in Argo CD’s repository credentials handler can crash the server when concurrent operations target the same repository URL. An attacker with a valid API token granting repository create, update, or delete permissions can repeatedly trigger the crash, keeping the server unavailable.
Teams running Argo CD 2.1.0–2.14.19, 3.2.0-rc1, 3.1.0-rc1–3.1.7, or 3.0.0-rc1–3.0.18, or using the Go package github.com/argoproj/argo-cd, should check their deployments.