Cross-Site Scripting (XSS) in auth0-lock (CVE-2020-15119)
Summary
Cross-site scripting in auth0-lock (CVE-2020-15119). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 11.26.3 or later.
Original description
The description as published by the source.
In auth0-lock versions before and including 11.25.1, dangerouslySetInnerHTML is used to update the DOM. When dangerouslySetInnerHTML is used, the application and its users might be exposed to cross-site scripting (XSS) attacks.
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-2020-15119 has been found in auth0-lock.
Risk of unauthorized operations or information disclosure.
What to do: upgrade auth0-lock to 11.26.3 or later.
If unsure, ask your IT team or search "auth0-lock CVE-2020-15119" on the vendor's site.
CVE-2020-15119 (auth0-lock) — CWE-79
Attack vector: remote (network-reachable)
Patched: 11.26.3 — 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.
Check the vendor advisory for the affected versions of auth0-lock.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 11.26.3.
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.26.3ステージング環境で 11.26.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- web github.com