Most recent entries from all

bdu:2022-06147

EUVD-2026-233556

fkie_cve-2022-39263

`@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.

GHSA-4rxr-27mm-mxq9 — Upstash Adapter missing token verification

Affected: npm: @next-auth/upstash-redis-adapter

### Impact Applications that use `next-auth` Email Provider and `@next-auth/upstash-redis-adapter` before v3.0.2 are affected.

### Description 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.

### Patches The vulnerability is patched in v3.0.2. To upgrade, run one of the following: ``` npm i @next-auth/upstash-redis-adapter@latest ``` ``` yarn add @next-auth/upstash-redis-adapter@latest ``` ``` pnpm add @next-auth/upstash-redis-adapter@latest ```

### Workarounds Using Advanced Initialization, developers can check the requests and compare the query's token and identifier before proceeding. Below is an example of how to do this: (Upgrading is still strongly recommended)

```js import { createHash } from "crypto" export default async function auth(req, res) { if (req.method === "POST" && req.action === "callback") { const token = req.query?.token const identifier = req.query?.email function hashToken(token: string) { const provider = authOptions.providers.find((p) => p.id === "email") const secret = authOptions.secret return ( createHash("sha256") // Prefer provider specific secret, but use default secret if none specified…

Most recent entries from all

bdu:2022-06147

EUVD-2026-233556

fkie_cve-2022-39263

GHSA-4rxr-27mm-mxq9 — Upstash Adapter missing token verification

gsd-2022-39263