workflow
Affected
- introduced
0, fixed4.2.0-beta.64(semver)
Fixed versions
4.2.0-beta.64
Fix
- Fixed version
4.2.0-beta.64npm install [email protected]
Advisory
Also known as: None
Vercel Workflow Allows Webhook Creation with Predictable User-Specified Tokens
createWebhook() in Vercel Workflow DevKit accepts a user-specified token parameter that serves as the credential for the public webhook endpoint /.well-known/workflow/v1/webhook/{token}. Official documentation recommended predictable token patterns, making it possible for an unauthenticated remote attacker to guess the token and inject arbitrary payloads into the workflow execution context.
Impact
An attacker who guesses a webhook token can resume the associated workflow with an attacker-controlled HTTP request body, potentially triggering downstream side effects such as API calls, database writes, or deployments.
Fix
token option from createWebhook() so that webhook tokens are always randomly generated by the SDK.Workarounds
In case a version upgrade is not possible, avoid passing predictable or guessable values to the token parameter of createWebhook(). Instead, users can either
createWebhook() to createHook() instead and programmatically resume hooks using resumeHook() instead of the public webhook endpoint, orcreateWebhook() without passing a user-provided token, which uses a non-guessable random nanoid by default.Medium Basis: The source's own band: MODERATE
0, fixed 4.2.0-beta.64 (semver)4.2.0-beta.64
4.2.0-beta.64npm install [email protected]0, fixed 4.2.0-beta.64 (semver)4.2.0-beta.64
4.2.0-beta.64npm install @workflow/[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