CVE-2023-31999
Description
All versions of @fastify/oauth2 used a statically generated state parameter at startup time and were used across all requests for all users. The purpose of the Oauth2 state parameter is to prevent Cross-Site-Request-Forgery attacks. As such, it should be unique per user and should be connected to the user's session in some way that will allow the server to validate it. v7.2.0 changes the default behavior to store the state in a cookie with the http-only and same-site=lax attributes set. The state is now by default generated for every user. Note that this contains a breaking change in the checkStateFunction function, which now accepts the full Request object.
How to fix
- fastify oauth27.2.0 or later
- @fastify/oauth27.2.0 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| fastify oauth2 | v < 7.2.0 | 7.2.0 |
| @fastify/oauth2npm | v < 7.2.0 | 7.2.0 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.