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.
Remediation
References
https://auth0.com/docs/secure/attack-protection/state-parameters
https://github.com/fastify/fastify-oauth2/releases/tag/v7.2.0
https://hackerone.com/reports/2020418
Related Vulnerabilities
CVE-2017-1000427 Vulnerability in maven package org.webjars:marked
CVE-2020-16022 Vulnerability in maven package org.webjars.npm:electron
CVE-2020-7639 Vulnerability in npm package @eivifj/dot
CVE-2017-16198 Vulnerability in npm package ritp
CVE-2023-29519 Vulnerability in maven package org.xwiki.platform:xwiki-platform-attachment-ui