Cross-Site Scripting (XSS) in @auth0/nextjs-auth0 (CVE-2021-32702)
Summary
Cross-site scripting in @auth0/nextjs-auth0 (CVE-2021-32702). Risk of unauthorized operations or information disclosure. Exploitable via error. Mitigation: upgrade to 1.4.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 and including 1.4.1 are vulnerable to reflected XSS. An attacker can execute arbitrary code by providing an XSS payload in the error query parameter which is then processed by the callback handler as an error message. You are affected by this vulnerability if you are using @auth0/nextjs-auth0 version 1.4.1 or lower unless you are using custom error handling that does not return the error message in an HTML response. Upgrade to version 1.4.1 to resolve. The fix adds basic HTML escaping to the error message and it should not impact your users.
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-32702 has been found in @auth0/nextjs-auth0.
Attackers can target a specific entry point like error over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @auth0/nextjs-auth0 to 1.4.2 or later.
If unsure, ask your IT team or search "@auth0/nextjs-auth0 CVE-2021-32702" on the vendor's site.
CVE-2021-32702 (@auth0/nextjs-auth0) — CWE-79
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: error
Patched: 1.4.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.
Cross-site scripting (XSS) (CWE-79) exists in @auth0/nextjs-auth0. Attackers reach the vulnerable code path via error without authentication.
Check the vendor advisory for the affected versions of @auth0/nextjs-auth0. Attack surface: error.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.4.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.4.2ステージング環境で 1.4.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- web npmjs.com
- web npmjs.com