Vulnerability · Published Jul 4, 2023 · Assigned by hackerone

CVE-2023-31999

High 8.8

In plain English

A high-severity security flaw in @fastify/oauth2 from npm. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.7% (higher than 54% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)8.8High
Exploit odds (30 days)0.7%top 46.5% of all CVEs
Exploited in the wildNo reportsCISA SSVC: poc
Attack toolingNoneno public tooling known

Official 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 packages & fixed versions

EcosystemPackageFixed inAdvisory
npm@fastify/oauth27.2.0GHSA-g8x5-p9qc-cf95

Affected products (as reported)

VendorProductVersions
npm @fastify/oauth2 v7.2.0 – before v7.2.0

References