| Gói / sản phẩm | Phiên bản bị ảnh hưởng | Phiên bản đã vá |
|---|---|---|
| @clerk/astro | ≥ 2.9.0, < 2.10.2 | 2.10.2 |
| @clerk/backend | ≥ 2.0.0, < 2.4.0 | 2.4.0 |
| @clerk/express | ≥ 1.6.0, < 1.7.4 | 1.7.4 |
| @clerk/fastify | ≥ 2.3.0, < 2.4.4 | 2.4.4 |
| @clerk/nextjs | ≥ 6.2.10, < 6.23.3 | 6.23.3 |
| @clerk/nuxt | ≥ 1.7.0, < 1.7.5 | 1.7.5 |
| @clerk/react-router | ≥ 1.5.0, < 1.6.4 | 1.6.4 |
| @clerk/remix | ≥ 4.8.0, < 4.8.5 | 4.8.5 |
| @clerk/tanstack-react-start | ≥ 0.16.0, < 0.18.3 | 0.18.3 |
Applications that use the verifyWebhook() helper to verify incoming Clerk webhooks are susceptible to accepting improperly signed webhook events.
@clerk/backend: the helper has been patched as of 2.4.0@clerk/astro: the helper has been patched as of 2.10.2@clerk/express: the helper has been patched as of 1.7.4@clerk/fastify: the helper has been patched as of 2.4.4@clerk/nextjs: the helper has been patched as of 6.23.3@clerk/nuxt: the helper has been patched as of 1.7.5@clerk/react-router: the helper has been patched as of 1.6.4@clerk/remix: the helper has been patched as of 4.8.5@clerk/tanstack-react-start: the helper has been patched as of 0.18.3The issue was resolved in @clerk/backend 2.4.0 by:
If unable to upgrade, developers can workaround this issue by verifying webhooks manually, per this documentation.
Bạn đang dùng một trong các sản phẩm này? Quét site để biết có đang lộ phiên bản có lỗ hổng không.
Quét site miễn phí