SupersetApplication · Apache
CVE-2024-24779
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 · uneditedApache Superset with custom roles that include `can write on dataset` and without all data access permissions, allows for users to create virtual datasets to data they don't have access to. These users could then use those virtual datasets to get access to unauthorized data. This issue affects Apache Superset: before 3.0.4, from 3.1.0 before 3.1.1. Users are recommended to upgrade to version 3.1.1 or 3.0.4, which fixes the issue.
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 contains an access control bypass where users with custom roles granted the `can write on dataset` permission (but lacking full data access permissions) can create virtual datasets that expose data they are not authorized to access. This authorization flaw allows privilege escalation through virtual dataset creation, bypassing intended data access controls.
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
<= 3.0.4>= 3.1.0, < 3.1.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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 Apache Superset versionCheck the Superset version through the UI under Settings > About, or by running `superset version` if CLI access is available, or inspect the version in the package metadata (pyproject.toml or setup.py)Affected if The installed version is <= 3.0.4 OR >= 3.1.0 and < 3.1.1
-
Review custom roles with dataset write permissionsNavigate to Settings > List of Roles in the Superset UI, or query the Superset database (tables: ab_role_permission_view, role) to identify custom roles assigned the `can write on dataset` permissionAffected if Custom roles exist that have the `can write on dataset` permission granted
-
Verify role lacks full data accessFor each custom role with `can write on dataset`, confirm it does NOT have full dataset access permissions (such as `datasource access` on all databases or `all_datasource_access`)Affected if The custom role has `can write on dataset` but lacks full data access permissions, creating the vulnerable configuration
-
Confirm virtual dataset capability is enabledCheck if the `can write on VirtualDataset` permission exists and is assigned, or verify virtual datasets can be created under SQL > Virtual Datasets in the UIAffected if Users with the vulnerable role combination can create virtual datasets in the environment
Your environment is affected if running a vulnerable Superset version AND you have custom roles with `can write on dataset` permission that lack full data access, allowing those users to potentially access data outside their authorized scope via virtual datasets.
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 · scoped3.1.1
Upgrade Apache Superset to version 3.1.1 or 3.0.4 to receive the patch for this authorization bypass vulnerability.
3.1.1 (latest stable) or 3.0.4 (LTS)
- Back up your current Apache Superset installation and database before upgrading
- Stop the Superset service to prevent data inconsistencies during upgrade
- Upgrade Superset using your installation method: for pip installations, run 'pip install apache-superset==3.1.1' (or '==3.0.4' for the LTS version)
- Run database migrations with 'superset db upgrade' or equivalent for your setup
- Restart the Superset service
- Verify the upgrade was successful and test that the authorization controls now properly restrict virtual dataset creation
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Superset
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24779 — 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-2024-24779 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