CVE-2023-27524
Apache Superset contains an insecure default initialization of a resource vulnerability that allows an attacker to authenticate and access unauthorized resources on installations that have not altered the default configured SECRET_KEY according to installation instructions.
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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L- lists.apache.org/thread/n0ftx60sllf527j7g11kmt24wvof8xykMailing ListVendor Advisory
- packetstormsecurity.com/files/172522/Apache-Superset-2.0.0-Authentication-Bypass.htmlExploitThird Party Advisory
- packetstormsecurity.com/files/175094/Apache-Superset-2.0.0-Remote-Code-Execution.htmlExploitThird Party Advisory
- openwall.com/lists/oss-security/2023/04/24/2Mailing List
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-27524Third Party AdvisoryUS Government Resource
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 1002 days
- CVSS
- 8.9 HIGH
- EPSS (30-day exploit probability)
- 98.1% · top 1% of all CVEs
- Weakness
- CWE-1188
- Attack vector
- Network, remotely reachable
- Preconditions
- No privileges and no user interaction
- 1.Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.