SupersetApplication · Apache
CVE-2023-46104
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 · uneditedUncontrolled 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 confidenceApache Superset's import functionality for databases, dashboards, and datasets does not properly validate ZIP file contents before extraction. An authenticated attacker can upload a malicious ZIP file (zip bomb) that causes uncontrolled resource consumption, potentially leading to denial of service.
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
< 2.1.3>= 3.0.0, < 3.0.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Superset versionRun 'pip show apache-superset' or check the version via the Superset UI at Settings > About, or query the /api/v1/version API endpointAffected if The installed version is less than 2.1.3, OR greater than or equal to 3.0.0 but less than 3.0.1
-
Confirm import feature is accessibleVerify the import endpoints (/api/v1/import/) are available by checking if you can access the import option under Settings > Import in the Superset UIAffected if The import functionality is enabled and reachable without additional access restrictions beyond basic authentication
-
Verify authentication is required for importsCheck that the Superset application requires valid user credentials to access the import functionality by attempting to use the import feature without logging in or with a low-privilege accountAffected if The import feature can be accessed by any authenticated user, including potentially untrusted users
-
Check resource limits on import operationsInspect the Superset configuration (superset_config.py) for ZIP_FILE_MAX_SIZE and EXTRACT_MAX_COMPRESSED_SIZE settings, or check if any web server (nginx, apache) has client_max_body_size limits setAffected if No extraction size limits, file size limits, or resource consumption controls are configured for the import functionality
You are affected if your Superset version falls within the vulnerable range (< 2.1.3 or >= 3.0.0 to < 3.0.1) AND the import feature is accessible to authenticated users without strict resource limits enforced.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.1.33.0.1
Implement file size limits and extraction depth controls in the import functionality to prevent zip bomb attacks. Upgrade to Apache Superset version 2.1.3 or 3.0.2 or later where available.
2.1.3 or 3.0.1
- Backup the Superset database and configuration files before proceeding
- Review the official Apache Superset upgrade documentation for guidance on upgrading to your target version
- Upgrade Apache Superset to version 2.1.3 (if currently on 2.x) or version 3.0.1 (if currently on 3.x)
- After upgrade, verify the version by checking the Superset About page or using the superset version command
- Test that the import functionality for databases, dashboards, and datasets works correctly with ZIP files
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Superset
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46104 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-46104 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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