Vulnerability in next-auth (CVE-2021-21310)
Summary
Vulnerability in next-auth (CVE-2021-21310). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.3.0 or later.
Original description
The description as published by the source.
Impact
Implementations using the Prisma database adapter with the Email provider are impacted.
Implementations using the Prisma database adapter that are not using the Email provider are not impacted.
Implementations using the default database adapter (TypeORM) with the Email provider are not impacted.
Implementations not using a database are not impacted.
Patches
This issue is fixed in 3.3.0 and newer versions.
Workarounds
Those not able to upgrade can alternatively disable the Email provider as a workaround.
Description
The Prisma database adapter was checking the verification token but not the identifier (the email address associated with the token). This made it possible to use a valid token assigned to one user, to sign in as another user when using the Prima adapter in conjunction with the Email provider. The defect is specific to the community-supported Prisma database adapter in versions <3.3.0 and is not present in the default database adapter (TypeORM).
Note: The current community-supported adapter was not developed by Prisma.
The defect was a problem in the implementation of verification function the adapter and is not directly related to Prisma.
The flaw may exist in other third party database adapters that do not check both the identifier and token values.
The design of the database adapter API may be revised in future to help reduce the likelyhood of similar defects.
Timeline
On Monday (2021-02-08) we were notifie…
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-21310 has been found in next-auth.
Risk of unauthorized operations or information disclosure.
What to do: upgrade next-auth to 3.3.0 or later.
If unsure, ask your IT team or search "next-auth CVE-2021-21310" on the vendor's site.
CVE-2021-21310 (next-auth) — CWE-290
Patched: 3.3.0 — apply immediately
Workaround: Those not able to upgrade can alternatively disable the Email provider as a workaround.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-290) exists in next-auth.
Check the vendor advisory for the affected versions of next-auth.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 3.3.0.
Workaround: Those not able to upgrade can alternatively disable the Email provider as a workaround.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'next-auth' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'next-auth' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
next-authを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Those not able to upgrade can alternatively disable the Email provider as a workaround.パッチが適用されるまでの応急処置として、Those not able to upgrade can alternatively disable the Email provider as a workaround. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade next-auth to 3.3.0ステージング環境で 3.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com
- web npmjs.com