Open Redirect in @auth0/nextjs-auth0 (CVE-2021-43812)
Summary
Vulnerability in @auth0/nextjs-auth0 (CVE-2021-43812). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.6.2 or later.
Original description
The description as published by the source.
The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. Versions before 1.6.2 do not filter out certain returnTo parameter values from the login url, which expose the application to an open redirect vulnerability. Users are advised to upgrade as soon as possible. There are no known workarounds for this issue.
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-43812 has been found in @auth0/nextjs-auth0.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @auth0/nextjs-auth0 to 1.6.2 or later.
If unsure, ask your IT team or search "@auth0/nextjs-auth0 CVE-2021-43812" on the vendor's site.
CVE-2021-43812 (@auth0/nextjs-auth0) — CWE-601
Attack vector: remote (network-reachable) / unauthenticated
Patched: 1.6.2 — apply immediately
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-601) exists in @auth0/nextjs-auth0.
Check the vendor advisory for the affected versions of @auth0/nextjs-auth0.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.6.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@auth0/nextjs-auth0' . 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 '@auth0/nextjs-auth0' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@auth0/nextjs-auth0を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @auth0/nextjs-auth0 to 1.6.2ステージング環境で 1.6.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com