Cross-Site Scripting (XSS) in auth0-lock (CVE-2021-32641)
Summary
Cross-site scripting in auth0-lock (CVE-2021-32641). Risk of unauthorized operations or information disclosure. Exploitable via flashMessage. Mitigation: upgrade to 11.30.1 or later.
Original description
The description as published by the source.
auth0-lock is Auth0's signin solution. Versions of nauth0-lock before and including 11.30.0 are vulnerable to reflected XSS. An attacker can execute arbitrary code when the library's flashMessage feature is utilized and user input or data from URL parameters is incorporated into the flashMessage or the library's languageDictionary feature is utilized and user input or data from URL parameters is incorporated into the languageDictionary. The vulnerability is patched in version 11.30.1.
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-32641 has been found in auth0-lock.
Attackers can target a specific entry point like flashMessage over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade auth0-lock to 11.30.1 or later.
If unsure, ask your IT team or search "auth0-lock CVE-2021-32641" on the vendor's site.
CVE-2021-32641 (auth0-lock) — CWE-79
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: flashMessage / languageDictionary
Patched: 11.30.1 — 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-lock. Attackers reach the vulnerable code path via flashMessage without authentication.
Check the vendor advisory for the affected versions of auth0-lock. Attack surface: flashMessage / languageDictionary.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 11.30.1.
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-lock' . 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-lock' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
auth0-lockを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade auth0-lock to 11.30.1ステージング環境で 11.30.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- report github.com