Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2023-27524 CISA KEV high

[KEV] Vulnerability in Apache Superset (CVE-2023-27524)

Summary

Vulnerability in Apache Superset (CVE-2023-27524). Confidential information can be exposed externally. Listed in CISA KEV — actively exploited. Mitigation: upgrade to 2.0.2 or later.

Original description

The description as published by the source.

Session Validation attacks in Apache Superset versions up to and including 2.0.1. Installations that have not altered the default configured SECRET_KEY according to installation instructions allow for an attacker to authenticate and access unauthorized resources. This does not affect Superset administrators who have changed the default value for SECRET_KEY config.

All superset installations should always set a unique secure random SECRET_KEY. Your SECRET_KEY is used to securely sign all session cookies and encrypting sensitive information on the database.
Add a strong SECRET_KEY to your superset_config.py file like:

SECRET_KEY =

Alternatively you can set it with SUPERSET_SECRET_KEY environment variable.

Source: CISA Known Exploited Vulnerabilities NVD GitHub Advisory CISA KEV

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-2023-27524 has been found in Apache Superset.
Confidential information can be exposed externally.
Note: CISA has officially confirmed this is actively exploited in the wild. Treat it with elevated urgency.
What to do: upgrade Apache Superset to 2.0.2 or later.
If unsure, ask your IT team or search "Apache Superset CVE-2023-27524" on the vendor's site.

CVE-2023-27524 (Apache Superset) — CWE-1188
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.0.2 — apply immediately
Listed in CISA KEV — actively exploited, treat as top priority.
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-1188) exists in Apache Superset.

📍 Affected scope

Check the vendor advisory for the affected versions of Apache Superset.

🔥 Severity

Severity: High. Confidential information can be exposed externally. Listed in CISA KEV — actively exploited in the wild, treat as top priority.

🔧 How to fix

Update to 2.0.2.

🛡️ 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'superset' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で superset を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Consider incident declaration escalate 
    Notify SOC / on-call

    CISA KEV登録済 = 実環境で悪用が観測されている。侵入の兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。

  3. 3
    Apply patch patch 
    Upgrade Apache Superset to 2.0.2

    ステージング環境で 2.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Bitnami superset
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.0.2"}]}]
PyPI apache-superset
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details