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-2022-21164 Vulnerability in npm package node-lmdb
CVE-2023-50572 Vulnerability in maven package org.jline:jline-console
CVE-2020-21485 Vulnerability in maven package org.alluxio:alluxio-parent
CVE-2019-1010091 Vulnerability in maven package org.webjars.bower:tinymce
CVE-2021-27516 Vulnerability in maven package org.webjars.bower:urijs