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://hackerone.com/reports/2020418
https://github.com/fastify/fastify-oauth2/releases/tag/v7.2.0
Related Vulnerabilities
CVE-2020-5245 Vulnerability in maven package io.dropwizard:dropwizard-validation
CVE-2020-28423 Vulnerability in npm package monorepo-build
CVE-2022-24279 Vulnerability in npm package madlib-object-utils
CVE-2020-28487 Vulnerability in maven package org.webjars.bowergithub.visjs:vis-timeline
CVE-2022-21724 Vulnerability in maven package org.postgresql:postgresql