CVE-2022-31093 json
Improper Handling of `callbackUrl` parameter in next-auth
published 4y ago modified 4mo ago also GHSA-g5fm-jp9v-2432 , EUVD-2022-6046
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
NextAuth.js is a complete open source authentication solution for Next.js applications. In affected versions an attacker can send a request to an app using NextAuth.js with an invalid `callbackUrl` query parameter, which internally is converted to a `URL` object. The URL instantiation would fail due to a malformed URL being passed into the constructor, causing it to throw an unhandled error which led to the **API route handler timing out and logging in to fail**. This has been remedied in versions 3.29.5 and 4.5.0. If for some reason you cannot upgrade, the workaround requires you to rely on Advanced Initialization. Please see the documentation for more.
Patch / fix
- npm next-auth 3.29.5, 4.5.0
- nextauth.js next-auth 3.29.5, 4.5.0
Is CVE-2022-31093 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
1.75% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | next-auth | <3.29.5 >=4.0.0, <4.5.0 |
3.29.5 4.5.0 |
Affected products
- nextauthjs next-auth
Classification
- Weakness
-
- CWE-754 Improper Check for Unusual or Exceptional Conditions
References
-
github.com
/nextauthjs/next-auth/commit/25517b73153332d948114bacdff3b5908de91d85
web, patch, third-party-advisory
-
github.com
/nextauthjs/next-auth/commit/e498483b23273d1bfc81be68339607f88d411bd6
web, patch, third-party-advisory
-
next-auth.js.org
/configuration/initialization#advanced-initialization
web, vendor-advisory
-
github.com
/nextauthjs/next-auth/security/advisories/GHSA-g5fm-jp9v-2432
web, mitigation, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-31093
advisory
-
github.com
/nextauthjs/next-auth
package
Sources
- CVE List CVE-2022-31093
- GitHub Advisory GHSA-g5fm-jp9v-2432
- NVD CVE-2022-31093
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.