dbcve.org
SupersetApplication · Apache

CVE-2024-24773

MEDIUM · 6.5 CVSS v3.1 Published 2024-02-28
Fix available
A fix is available. Upgrade to 3.0.4 / 3.1.1 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
Improper parsing of nested SQL statements on SQLLab would allow authenticated users to surpass their data authorization scope. 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, 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 confidence

Apache Superset's SQLLab has improper parsing of nested SQL statements that allows authenticated users to bypass data authorization controls and access data beyond their permitted scope. This is an authorization bypass vulnerability in the SQL parsing layer.

MitigationUpgrade Apache Superset to version 3.1.1 or later to resolve the improper SQL parsing vulnerability.

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:< 3.0.4>= 3.1.0, < 3.1.1

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
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 checks

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

  1. Identify installed Apache Superset version
    Run the command to display the Superset version (commonly via superset version command, pip show apache-superset, or check the package metadata)
    Affected if The installed version is < 3.0.4 OR >= 3.1.0 AND < 3.1.1
  2. Confirm SQLLab is enabled
    Check the Superset configuration file (superset_config.py) for the SQLLAB_ENABLED setting or equivalent feature flag
    Affected if SQLLab is enabled and accessible to users
  3. Verify data access controls exist
    Review the configured database connections and their associated role-based access control (RBAC) settings in Superset, checking which databases users can query through SQLLab
    Affected if Users have SQLLab access to databases with defined but potentially bypassable row-level security policies
  4. Test for nested SQL parsing behavior
    Execute a test query through SQLLab containing nested SQL statements (such as subqueries or statements using LIMIT in unexpected ways) against a dataset with restricted access
    Affected if A user can retrieve data from tables or schemas outside their authorized scope using nested SQL constructs

A user is affected if their Superset version is vulnerable (less than 3.0.4 or between 3.1.0 and 3.1.1) and they have SQLLab access that can be exploited through nested SQL statement parsing to bypass data authorization 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 3.0.4 / 3.1.1 or later
Fixed in 3.0.43.1.1
Interim mitigation

Upgrade Apache Superset to version 3.1.1 or later to resolve the improper SQL parsing vulnerability.

Recommended fix High confidence

3.1.1

  1. Backup the current Superset installation and database before proceeding with the upgrade
  2. Stop the Superset service to prevent data inconsistencies during upgrade
  3. If using pip: Run 'pip install apache-superset==3.1.1' to upgrade to the fixed version
  4. If using Docker: Pull the Apache Superset 3.1.1 image and restart the container
  5. If using a package manager (apt/yum): Update the package index and install apache-superset version 3.1.1
  6. Run database migrations if required: 'superset db upgrade'
  7. Restart the Superset service
  8. Verify the upgrade was successful by checking the Superset version in the UI or via 'superset version'
Caveat Review the Apache Superset 3.1.1 release notes for any breaking changes or deprecations before upgrading

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-24773 — 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-24773 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