CVE-2023-27524
CVE-2023-27524 — Apache Superset Insecure Default Initialization of Resource Vulnerability
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.
Published Updated Sources: NVD, CISA, FIRST EPSS
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Confirmed
CISA KEV, listed Jan 8, 2024
EPSS
97%
ahead of 99.9% of scored CVEs
CVSS base
9.8
critical · 2 sources
CISA SSVC assessment
Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.
Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script all four kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component
Remediation
The vendor's own words where we have them.
Upgrade apache_superset to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.
CISA required action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Federal deadline Jan 29, 2024 — passed 963 days ago
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Treat as emergency remediation because CISA KEV status is present.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| apache | apache_superset | — | Vulnerable |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Availability
High
Confidentiality
High
Integrity
High
Scope
Unchanged
Attack Complexity
Low
Attack Vector
Network
Privileges Req
None
User Interaction
None
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 8.9 | CVSS 3.1 | high | 2.2 | 6 | apache.org (CNA) |
| 9.8 | CVSS 3.1 | critical | 3.9 | 5.9 | NVD |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L
Weakness & attack patterns
- CWE-1188
Inferred from the weakness class — not observed against this CVE.
- T1211Exploitation for Defensive Evasion
- T1542.002Pre-OS Boot: Component Firmware
- T1556Modify Authentication Process
CISA KEV details
CISA lists a CVE here once it has evidence of exploitation against real targets.
Listed
Jan 8, 2024
Federal deadline
Jan 29, 2024
passed 963 days ago
Ransomware use
Unknown
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Exploit entries
1
Exploit-DB and CTI exploit indexes
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Prioritize edge telemetry for network-reachable apache_superset.
- Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Added · CVSS 3.1 9.8 (AV:N)
Jun 17, 2026 · NVD
- 2024
Added to CISA KEV catalog
Jan 8, 2024 · CISA
- 2023
Initial · CVE published
Apr 24, 2023 · NVD
References
6 on the record
- lists.apache.org/thread/n0ftx60sllf527j7g11kmt24wvof8xyk
Mailing List, Vendor Advisory
- packetstormsecurity.com/files/172522/Apache-Superset-2.0.0-Authentication-Bypass.html
Exploit, Third Party Advisory, VDB Entry
- packetstormsecurity.com/files/175094/Apache-Superset-2.0.0-Remote-Code-Execution.html
Exploit, Third Party Advisory, VDB Entry
- www.openwall.com/lists/oss-security/2023/04/24/2
Mailing List
- www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-27524
Third Party Advisory, US Government Resource
- nvd.nist.gov/vuln/detail/CVE-2023-27524
Vendor Advisory
Elsewhere on this site
- apacheevery CVE for this vendor
- January 2024what else CISA listed
- Unclassifiedsame class
- CWE-1188other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2023-27524 is Apache Superset Insecure Default Initialization of Resource Vulnerability, a critical vulnerability affecting apache_superset from apache. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 1 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.8 describes technical severity, while EPSS 97% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.