Description
The setWebhookResolver in packages/api/src/resolvers/webhooks/index.ts stores the caller-supplied url without any address validation, and the file imports no validation helper. When a subscribed event fires, callWebhook in packages/api/src/jobs/call_webhook.ts issues axios.request with that url, the method and Content-Type recorded on the webhook, and a JSON body carrying the event data, so an authenticated user can make the server send repeated attacker-shaped requests to internal endpoints, including link-local metadata addresses. The request is blind: callWebhook discards the result and writes only a success line or the axios error to the server log, so the response is not returned through the API.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| omnivore-app | omnivore | — | — |
References
- GitHub Issue #4647 issue-tracking
- fix(): fix ssrf via scan feeds and webhooks (#4656) patch
- setWebhookResolver storing the URL unvalidated before the fix technical-description
- callWebhook dispatching axios.request to the stored URL technical-description
- https://github.com/omnivore-app/omnivore product
- VulnCheck Advisory: Omnivore Stored Server-Side Request Forgery via the setWebhook Mutation third-party-advisory