Vulnerability 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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Fastify | Oauth2 | < 7.2.0 |
Related Weaknesses (CWE)
References
- https://auth0.com/docs/secure/attack-protection/state-parametersExploit
- https://github.com/fastify/fastify-oauth2/releases/tag/v7.2.0Release Notes
- https://hackerone.com/reports/2020418Permissions Required
- https://auth0.com/docs/secure/attack-protection/state-parametersExploit
- https://github.com/fastify/fastify-oauth2/releases/tag/v7.2.0Release Notes
- https://hackerone.com/reports/2020418Permissions Required
FAQ
What is CVE-2023-31999?
CVE-2023-31999 is a vulnerability with a CVSS score of 8.8 (HIGH). 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 Cro...
How severe is CVE-2023-31999?
CVE-2023-31999 has been rated HIGH with a CVSS base score of 8.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2023-31999?
Check the references section above for vendor advisories and patch information. Affected products include: Fastify Oauth2.