First published: Wed Sep 28 2022(Updated: )
`@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.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Nextauth.js Next-auth | <3.0.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
`CVE-2022-39263` is a vulnerability affecting `@next-auth/upstash-redis-adapter` in NextAuth.js, which provides authentication for Next.js applications using the Email Provider.
The severity of `CVE-2022-39263` is high with a severity value of 8.1.
`CVE-2022-39263` can cause issues with authentication in Next.js applications that use the `next-auth` Email Provider and `@next-auth/upstash-redis-adapter` before version 3.0.2.
To fix `CVE-2022-39263`, make sure to update `@next-auth/upstash-redis-adapter` to version 3.0.2 or later.
More information about `CVE-2022-39263` can be found in the following references: [GitHub Commit](https://github.com/nextauthjs/next-auth/commit/d16e04848ee703cf797724194d4ad2907fe125a9) and [GitHub Security Advisory](https://github.com/nextauthjs/next-auth/security/advisories/GHSA-4rxr-27mm-mxq9).