Loading HuntDB...
Hunt
Vulnerability Intelligence by wss.sh
Home Daily Briefings High Impact CVEs Recent Exploits KEV Catalog GitHub Advisories Latest Updates Security News
Sign In Sign Up

CVE-2023-31999

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

Expert Analysis

Professional remediation guidance

Get tailored security recommendations from our analyst team for CVE-2023-31999. We'll provide specific mitigation strategies based on your environment and risk profile.

No CVSS data available

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.

Available Exploits

No exploits available for this CVE.

Related News

No news articles found for this CVE.

Affected Products

npm

@fastify/oauth2

Affected Versions:

v7.2.0

GitHub Security Advisories

Community-driven vulnerability intelligence from GitHub

✓ GitHub Reviewed HIGH

@fastify/oauth2 vulnerable to Cross Site Request Forgery due to reused Oauth2 state

GHSA-g8x5-p9qc-cf95

Advisory Details

### Impact 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. ### Patches 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. ### Workarounds There are no known workarounds. ### References * [Prevent Attacks and Redirect Users with OAuth 2.0 State Parameters](https://auth0.com/docs/secure/attack-protection/state-parameters)

Affected Packages

npm @fastify/oauth2
ECOSYSTEM: ≥0 <7.2.0

CVSS Scoring

CVSS Score

7.5

CVSS Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N

References

WEB https://github.com/fastify/fastify-oauth2/security/advisories/GHSA-g8x5-p9qc-cf95
ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2023-35935
WEB https://github.com/fastify/fastify-oauth2/commit/bff756b456cbb769080631af2beb85671ff4c79c
WEB https://auth0.com/docs/secure/attack-protection/state-parameters
PACKAGE https://github.com/fastify/fastify-oauth2
WEB https://github.com/fastify/fastify-oauth2/releases/tag/v7.2.0

Advisory provided by GitHub Security Advisory Database. Published: July 5, 2023, Modified: July 6, 2023

References

https://hackerone.com/reports/2020418
https://auth0.com/docs/secure/attack-protection/state-parameters
https://github.com/fastify/fastify-oauth2/releases/tag/v7.2.0
Published: 2023-07-04T16:29:20.281Z
Last Modified: 2024-11-26T18:47:25.202Z
Copied to clipboard!