@clerk/backend Performs Insufficient Verification of Data Authenticity
clerk javascript
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @clerk/backend npm |
|
|
| @clerk/astro npm |
|
|
| @clerk/express npm |
clerk javascript
| Product | Affected | Fixed in |
|---|---|---|
| @clerk/backend npm |
|
|
| @clerk/astro npm |
|
|
| @clerk/express npm |
≥ 1.6.0 · < 1.7.4
|
| @clerk/fastify npm |
|
|
| @clerk/nextjs npm |
|
|
| @clerk/nuxt npm |
|
|
| @clerk/react-router npm |
|
|
| @clerk/remix npm |
|
|
| @clerk/tanstack-react-start npm |
|
|
Clerk helps developers build user management. Applications that use the verifyWebhook() helper to verify incoming Clerk webhooks are susceptible to accepting improperly signed webhook events. The issue was resolved in @clerk/backend 2.4.0.
From the CVE record · GitHub_M
Applications using the verifyWebhook() helper to verify incoming Clerk webhooks may accept improperly signed webhook events. An attacker could exploit this when an application processes an incoming webhook; the input does not specify authentication or user-interaction requirements.
Check applications using @clerk/backend >=2.0.0 <2.4.0, @clerk/astro >=2.9.0 <2.10.2, @clerk/express >=1.6.0 <1.7.4, @clerk/fastify >=2.3.0 <2.4.4, @clerk/nextjs >=6.2.10 <6.23.3, @clerk/nuxt >=1.7.0 <1.7.5, @clerk/react-router >=1.5.0 <1.6.4, @clerk/remix >=4.8.0 <4.8.5, or @clerk/tanstack-react-start >=0.16.0 <0.18.3.