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.
History

Tue, 26 Nov 2024 19:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}


cve-icon MITRE

Status: PUBLISHED

Assigner: hackerone

Published: 2023-07-04T16:29:20.281Z

Updated: 2024-11-26T18:47:25.202Z

Reserved: 2023-05-01T01:00:12.219Z

Link: CVE-2023-31999

cve-icon Vulnrichment

Updated: 2024-08-02T15:03:28.687Z

cve-icon NVD

Status : Modified

Published: 2023-07-04T17:15:10.657

Modified: 2024-11-21T08:02:30.127

Link: CVE-2023-31999

cve-icon Redhat

Severity : Moderate

Publid Date: 2023-07-04T00:00:00Z

Links: CVE-2023-31999 - Bugzilla