← Back
CVE-2023-42502
Open Redirect in superset (CVE-2023-42502)
Summary
vulnerability in superset (CVE-2023-42502). Risk of unauthorized operations or information disclosure. Exploitable via `Host header`. Mitigation: upgrade to `3.0.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2023-42502** has been found in superset.
Attackers can target a specific entry point like `Host header` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade superset to **3.0.0** or later.
If unsure, ask your IT team or search "superset CVE-2023-42502" on the vendor's site.
CVE-2023-42502 (superset) — CWE-601 /
Attack vector: remote (network-reachable)
Attack surface: Host header
Patched: `3.0.0` — 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.
❓ What is the problem
**A vulnerability** (CWE-601) exists in superset. Attackers reach the vulnerable code path via `Host header` without authentication.
📍 Affected scope
superset — . Attack surface: Host header.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.0.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'superset' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'superset' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `superset` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade superset to 3.0.0ステージング環境で 3.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Bitnami
superset
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.0.0"}]}]
PyPI
apache-superset
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2023-42502
- advisory https://github.com/advisories/GHSA-hc74-9vjm-c9xv
- package https://github.com/apache/superset
- package https://pypi.org/project/apache-superset
- web https://lists.apache.org/thread/n8348f194d8o8mln3oxd0s8jdl5bxbmn
- web http://www.openwall.com/lists/oss-security/2023/11/28/3