NextAuth.js: OAuth state, nonce, and PKCE check cookies are not bound to the provider that created them
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| nextauthjs | next-auth | affected |
|
|||||||||
| @auth | core | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Nextauth.js | Core |
|
||||||||||||
| Nextauth.js | Next-auth |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-x445-f3h2-j279 | Auth.js: OAuth state, nonce, and PKCE check cookies are not bound to the provider that created them |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.249% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Nextauth.js
Nextauth.js core Nextauth.js next-auth |
|
| Vendors & Products |
Nextauth.js
Nextauth.js core Nextauth.js next-auth |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | NextAuth.js provides authentication for Next.js. Prior to@auth/core 0.41.3 and next-auth 4.24.15 and 5.0.0-beta.32, Auth.js stores the OAuth/OIDC anti-CSRF checks state, nonce, and the PKCE verifier in global cookies that are not bound to the provider that created them. On callback, a check value minted during a sign-in started with one provider can satisfy the callback for a different provider because the stored cookie is not verified against the callback provider's identity, including the provider ID, issuer, client ID, or redirect URI. In a multi-provider application that permits account linking while logged in, when one provider's authorization request is observable and a target provider callback can be satisfied without a PKCE verifier, an attacker can lure a victim into starting a legitimate same-origin flow and link the attacker's target-provider account to the victim's Auth.js user. The linked provider grants the attacker persistent sign-in to the victim's account, while cross-site request forgery alone is insufficient. This issue is fixed in @auth/core 0.41.3 and next-auth 4.24.15 and 5.0.0-beta.32. | |
| Title | NextAuth.js: OAuth state, nonce, and PKCE check cookies are not bound to the provider that created them | |
| Weaknesses | CWE-345 CWE-346 CWE-940 |
|
| References |
|
|
| Metrics |
cvssV3_1
|