CVE-2023-27524: Apache Superset Insecure Default Initialization of Resource
Apache Superset · listed in the CISA catalog of actively exploited vulnerabilities since 2024-01-08.
- CVSS v3.1 (CVE record)
- 8.9
- high
- EPSS (exploit probability, 30 days)
- 98%
- among the highest 0.1% of all CVEs
- Added to CISA KEV
- 2024-01-08
- US federal due date 2024-01-29
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2023-27524 explained
CVE-2023-27524 is an insecure default configuration flaw in Apache Superset up to and including 2.0.1. Installations that kept the default SECRET_KEY allow an attacker to authenticate and access unauthorized resources. CISA lists it as known to be exploited, so administrators should verify their SECRET_KEY setting.
Impact
On installations that still use the default SECRET_KEY, a remote, unauthenticated attacker can authenticate and reach resources they should not access. No user interaction is needed, though attack complexity is rated high. Confidentiality and integrity impact are high and the scope is changed. CISA rates the technical impact as total but not automatable. Installations with a changed, unique SECRET_KEY are not affected.
Who is affected
Apache Software Foundation Apache Superset versions up to and including 2.0.1 are affected when the default SECRET_KEY has not been changed. The CVE record names no fixed version. The vendor's guidance is to set a unique, secure, random SECRET_KEY on every installation, which removes the exposure described in the record.
Written with AI from the data on this page and checked against it automatically.
Official description
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 = <YOUR_OWN_RANDOM_GENERATED_SECRET_KEY> Alternatively you can set it with SUPERSET_SECRET_KEY environment variable.
CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Apache Software Foundation Apache SupersetAffectedFixed in
- ≤ 2.0.1
not stated
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software Foundation Apache Superset |
| not stated |
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: lists.apache.org/thread/n0ftx60sllf527j7g11kmt24wvof8xyk
- CISA's deadline for US federal agencies: 2024-01-29 (passed) – a useful benchmark for everyone else, too.
What to do
- Check whether each Superset installation still uses the default SECRET_KEY.
- Set a unique, strong, randomly generated SECRET_KEY in superset_config.py or through the SUPERSET_SECRET_KEY environment variable.
- Follow the Apache vendor advisory for any further mitigations or updates.
- Restrict network access to Superset so it is not exposed to untrusted networks.
- Review logs and accounts for signs of unauthorized access, since the flaw is known to be exploited.
The CVE record names no fixed version. Apply the vendor's mitigation now: replace the default SECRET_KEY with a unique, secure random value. CISA's required action is to apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Check the vendor advisory for updates and limit network exposure meanwhile.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-1188 Insecure Default Initialization of Resource
Questions about CVE-2023-27524
- Is my Superset installation affected?
- It is affected if it runs version
2.0.1or earlier and still uses the default SECRET_KEY. Installations where administrators changed the default SECRET_KEY to their own value are not affected, according to the CVE description. - Is this vulnerability exploited in the wild?
- Yes. CISA added CVE-2023-27524 to its Known Exploited Vulnerabilities catalog on 2024-01-08, with a due date of 2024-01-29 for US federal agencies. Known ransomware use is listed as unknown.
- What does the SECRET_KEY protect?
- Superset uses the SECRET_KEY to sign all session cookies and to encrypt sensitive information in its database. A default key undermines both protections, which is why each installation needs its own secure random value.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.