CVE-2022-39263
Summary
| CVE | CVE-2022-39263 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2022-09-28 21:15:00 UTC |
| Updated | 2023-03-03 20:08:00 UTC |
| Description | `@next-auth/upstash-redis-adapter` is the Upstash Redis adapter for NextAuth.js, which provides authentication for Next.js. Applications that use `next-auth` Email Provider and `@next-auth/upstash-redis-adapter` before v3.0.2 are affected by this vulnerability. The Upstash Redis adapter implementation did not check for both the identifier (email) and the token, but only checking for the identifier when verifying the token in the email callback flow. An attacker who knows about the victim's email could easily sign in as the victim, given the attacker also knows about the verification token's expired duration. The vulnerability is patched in v3.0.2. A workaround is available. Using Advanced Initialization, developers can check the requests and compare the query's token and identifier before proceeding. |
Risk And Classification
Problem Types: CWE-287
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Next-auth | Nextauth | All | All | All | All |
| Application | Nextauth.js | Next-auth | All | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Missing token verification in Upstash Adapter · Advisory · nextauthjs/next-auth · GitHub | CONFIRM | github.com | |
| fix(adapters): check token during email verification in Upstash Adapt… · nextauthjs/next-auth@d16e048 · GitHub | MISC | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.