CVE-2023-31999

fastify-oauth2: CSRF due to reused Oauth2 state

Published Jul 4, 2023 CVSS 3.1 · 8.8 High EPSS < 1% KEV · Not listed
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

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2023-2056 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.
Github GHSA Github GHSA GHSA-g8x5-p9qc-cf95 @fastify/oauth2 vulnerable to Cross Site Request Forgery due to reused Oauth2 state
History
Type Values Removed Values Added
Metrics ssvc

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

Weaknesses

Sources

Status
PUBLISHED
Assigner
hackerone
Published
Updated
Nov 26, 2024, 6:47 PM
Reserved
May 1, 2023, 1:00 AM
Status
Modified
Published
Jul 4, 2023, 5:15 PM
Modified
Jun 17, 2026, 5:57 AM
Severity
Moderate
Public date
Jul 4, 2023, 12:00 AM