| Gói / sản phẩm | Phiên bản bị ảnh hưởng | Phiên bản đã vá |
|---|---|---|
| csrf-protection | ≥ 5.0.0, < 6.3.0< 4.1.0 | 6.3.04.1.0 |
| @fastify/csrf-protection | ≥ 5.0.0, < 6.3.0< 4.1.0 | 6.3.04.1.0 |
The CSRF protection enforced by the @fastify/csrf-protection library in combination with @fastify/cookie can be bypassed from network and same-site attackers under certain conditions.
@fastify/csrf-protection supports an optional userInfo parameter that binds the CSRF token to the user. This parameter has been introduced to prevent cookie-tossing attacks as a fix for CVE-2021-29624. Whenever userInfo parameter is missing, or its value can be predicted for the target user account, network and same-site attackers can 1. fixate a _csrf cookie in the victim's browser, and 2. forge CSRF tokens that are valid for the victim's session. This allows attackers to bypass the CSRF protection mechanism.
As a fix, @fastify/csrf-protection starting from version 6.3.0 (and v4.1.0) includes a server-defined secret hmacKey that cryptographically binds the CSRF token to the value of the cookie and the parameter, making tokens non-spoofable by attackers. This protection is effective as long as the parameter is unique for each user.
_csrfuserInfouserInfoThis is patched in version 6.3.0 and v4.1.0.
As a workaround, developers can use a random, non-predictable userInfo parameter for each user.
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í