dbcve.org
SupersetApplication · Apache

CVE-2024-23952

MEDIUM · 6.5 CVSS v3.1 Published 2024-02-14
Fix available
A fix is available. Upgrade to 2.1.3 / 3.0.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
This is a duplicate for CVE-2023-46104. With correct CVE version ranges for affected Apache Superset. Uncontrolled resource consumption can be triggered by authenticated attacker that uploads a malicious ZIP to import database, dashboards or datasets.   This vulnerability exists in Apache Superset versions up to and including 2.1.2 and versions 3.0.0, 3.0.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An authenticated attacker can upload a malicious ZIP file when importing databases, dashboards, or datasets in Apache Superset, causing uncontrolled resource consumption due to insufficient validation of the ZIP archive contents and size during the import process.

MitigationUpgrade Apache Superset to a version beyond 3.0.1 and 2.1.2 that includes the patch for CVE-2023-46104. As a compensating control, implement strict file size limits and ZIP extraction validation on import endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SupersetApplication
Affected:< 2.1.3>= 3.0.0, < 3.0.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Apache Superset version
    Run 'pip show apache-superset' or 'superset version' command to retrieve the installed version number
    Affected if Version is < 2.1.3 or >= 3.0.0 and < 3.0.2
  2. Verify import endpoints are accessible
    Check if the /api/v1/import/ endpoint or equivalent import routes are enabled and accessible to authenticated users
    Affected if Import functionality is enabled and users have import permissions
  3. Inspect file upload size configuration
    Review superset_config.py for FILE_UPLOAD_MAX_SIZE, MAX_CONTENT_LENGTH or similar upload limit settings
    Affected if No file size limits are configured or limits are set excessively high for ZIP imports
  4. Check ZIP extraction limits
    Review configuration for any extraction depth, file count, or decompression ratio limits applied to imported ZIP archives
    Affected if No extraction validation or resource consumption limits are defined for ZIP imports
  5. Review import operation logs
    Examine Superset logs for any large or repeated import requests, especially those that may have triggered resource exhaustion
    Affected if Logs show unusually large ZIP imports or resource consumption patterns on import endpoints

You are affected if your Superset version falls within the vulnerable ranges (< 2.1.3 or >= 3.0.0, < 3.0.2) AND import functionality is accessible to authenticated users without proper ZIP validation controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.1.3 / 3.0.2 or later
Fixed in 2.1.33.0.2
Interim mitigation

Upgrade Apache Superset to a version beyond 3.0.1 and 2.1.2 that includes the patch for CVE-2023-46104. As a compensating control, implement strict file size limits and ZIP extraction validation on import endpoints.

Recommended fix High confidence

Upgrade to Apache Superset 2.1.3 (if on 2.1.x) or 3.0.2 (if on 3.0.x)

  1. Identify your current Apache Superset version using the superset --version command or the version info in the UI
  2. If running version 2.1.2 or earlier, plan upgrade to version 2.1.3
  3. If running version 3.0.0 or 3.0.1, plan upgrade to version 3.0.2
  4. Review upgrade documentation at https://superset.apache.org/docs/installation/installing-superset-from-scratch
  5. Backup your current Superset database and configuration before upgrading
  6. Stop the Superset service
  7. Install the new version using pip: pip install apache-superset==2.1.3 (for 2.1.x) or apache-superset==3.0.2 (for 3.0.x)
  8. Run database migrations: superset db upgrade
Caveat Review Apache Superset release notes for version-specific changes between your current version and the target upgrade version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Superset Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23952 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-23952 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data