Apache · Superset · CWE-1188 · published 2023-04-24

CVE-2023-27524Apache Superset Insecure Default Initialization of Resource Vulnerability

This week Known exploited in the wild.

CVE-2023-27524 is actively exploited in the wild: CISA added it to the Known Exploited Vulnerabilities catalog on 2024-01-08. EPSS estimates a 98.1% chance of exploitation in the next 30 days, higher than 99% of all CVEs. This Superset vulnerability: CVSS 8.9 (v3.1), a successful attack gives total control of the component. CISA’s required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. US federal agencies must remediate by 2024-01-29. Patch this week.

Share this

Remediation#

CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. (federal due date 2024-01-29)

Patch events

  1. This weekExploited (KEV)CISA due 2024-01-29

    App server & middlewareApache Superset

    Insecure Default Initialization of ResourceCVE-2023-27524

    Why: Known exploited in the wild.

Exploit intelligence#

SignalValueSource
Known exploitedYes, added 2024-01-08CISA KEV
Ransomware useUnknownCISA KEV
EPSS (30-day exploitation probability)98% (100th pct)FIRST EPSS v2026.06.15
CVSS base score8.9 (v3.1)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L
CNA / CISA ADP
SSVC exploitationactiveCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

Weakness: CWE-1188: Initialization of a Resource with an Insecure Default

More from this vendor: all Apache vulnerabilities · recent KEV additions

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →