Vulnerabilities · 2023 · Fastify
CVE-2023-31999
Fastify Oauth2 vulnerability
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.
Affected products
Oauth2. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Fastify Oauth2 runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
More vulnerabilities in Fastify products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.