CVEvulnerability
CVE-2023-31999
8.8 HIGH
Official page ↗
- Status
- Modified
- Published
- 2023-07-04
- Last modified
- 2026-06-17
- Assigner
- [email protected]
- CVSS 3.1 ([email protected])
- 8.8 HIGH — CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Weaknesses
- CWE-352
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.
Affected configurations
• fastify oauth2 (< 7.2.0)
Related
Weakness · CWE (1)
- CWE-352 Cross-Site Request Forgery weakness
References
- https://auth0.com/docs/secure/attack-protection/state-parameters Exploit
- https://github.com/fastify/fastify-oauth2/releases/tag/v7.2.0 Release Notes
- https://hackerone.com/reports/2020418 Permissions Required
- https://auth0.com/docs/secure/attack-protection/state-parameters Exploit
- https://github.com/fastify/fastify-oauth2/releases/tag/v7.2.0 Release Notes
- https://hackerone.com/reports/2020418 Permissions Required