GHSA-4rxr-27mm-mxq9

Опубликовано: 30 сент. 2022

Источник: github

Github: Прошло ревью

CVSS3: 6.8

Описание

Upstash Adapter missing token verification

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)

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 .update(`${token}${provider.secret ?? secret}`) .digest("hex") ) } const hashedToken = hashToken(token) const invite = await authOptions.adapter.useVerificationToken?.({ identifier, token: hashedToken, }) if (invite.token !== hashedToken) { res.status(400).json({ error: "Invalid token" }) } } return await NextAuth(req, res, authOptions) }

References

EmailProvider: https://next-auth.js.org/providers/email Advanced Initialization: https://next-auth.js.org/configuration/initialization#advanced-initialization Upstash Redis Adapter: https://next-auth.js.org/adapters/upstash-redis

For more information

If you have any concerns, we request responsible disclosure, outlined here: https://next-auth.js.org/security#reporting-a-vulnerability

Ссылки

Пакеты

Наименование

@next-auth/upstash-redis-adapter

npm

Затронутые версииВерсия исправления

< 3.0.2

3.0.2

EPSS

Процентиль: 33%

0.00127

Низкий

6.8 Medium

CVSS3

CVE ID

CVE-2022-39263

Дефекты

CWE-287

Связанные уязвимости

CVE-2022-39263

CVSS3: 6.8

nvd

почти 3 года назад

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

BDU:2022-06147

CVSS3: 6.8

fstec

почти 3 года назад

Уязвимость программной платформы Node.js, связанная с ошибками реализации процедуры аутентификации, позволяющая нарушителю раскрыть защищаемую информацию

EPSS

Процентиль: 33%

0.00127

Низкий

6.8 Medium

CVSS3

CVE ID

CVE-2022-39263

Дефекты

CWE-287