dbcve.org
SupersetApplication · Apache

CVE-2024-39887

CRITICAL · 9.8 CVSS v3.1 Published 2024-07-16
Fix available
A fix is available. Upgrade to 4.0.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
An SQL Injection vulnerability in Apache Superset exists due to improper neutralization of special elements used in SQL commands. Specifically, certain engine-specific functions are not checked, which allows attackers to bypass Apache Superset's SQL authorization. To mitigate this, a new configuration key named DISALLOWED_SQL_FUNCTIONS has been introduced. This key disallows the use of the following PostgreSQL functions: version, query_to_xml, inet_server_addr, and inet_client_addr. Additional functions can be added to this list for increased protection. This issue affects Apache Superset: before 4.0.2. Users are recommended to upgrade to version 4.0.2, 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

SQL Injection vulnerability in Apache Superset allows attackers to bypass SQL authorization through unchecked engine-specific PostgreSQL functions (version, query_to_xml, inet_server_addr, inet_client_addr) that can be used to inject malicious SQL commands.

MitigationUpgrade to Apache Superset 4.0.2 or later. Alternatively, configure the new DISALLOWED_SQL_FUNCTIONS key in superset_config.py to block the identified functions and any additional engine-specific functions relevant to the deployment.

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:< 4.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Identify installed Apache Superset version
    Run `pip show apache-superset` or check the version in your package manager. Alternatively, check the About page in the Superset UI under Settings > About.
    Affected if Version is lower than 4.0.2 (e.g., 4.0.1, 3.x, 2.x series)
  2. Confirm PostgreSQL is used as a database backend
    Check superset_config.py for the SQLALCHEMY_DATABASE_URI setting. Look for postgresql:// or postgres:// in the connection string.
    Affected if The Superset metadata database runs on PostgreSQL and SQL Lab or external database connections are enabled
  3. Check if SQL Lab feature is enabled
    Inspect superset_config.py for ENABLE_GLOBAL_ASYNC_QUERIES, SQLLAB_ENABLED, or similar feature flags. Also check if users have access to SQL Lab in the UI.
    Affected if SQL Lab or ad-hoc SQL query functionality is available to users
  4. Verify if DISALLOWED_SQL_FUNCTIONS is configured
    Search superset_config.py for the DISALLOWED_SQL_FUNCTIONS configuration key. Check if it includes at least: version, query_to_xml, inet_server_addr, inet_client_addr
    Affected if DISALLOWED_SQL_FUNCTIONS is not defined, empty, or does not include the four identified PostgreSQL functions

You are affected if running Superset version < 4.0.2 with PostgreSQL backend and SQL Lab enabled, and the DISALLOWED_SQL_FUNCTIONS protection is not configured with the four identified functions.

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 4.0.2 or later
Fixed in 4.0.2
Interim mitigation

Upgrade to Apache Superset 4.0.2 or later. Alternatively, configure the new DISALLOWED_SQL_FUNCTIONS key in superset_config.py to block the identified functions and any additional engine-specific functions relevant to the deployment.

Recommended fix High confidence

4.0.2

  1. Upgrade Apache Superset to version 4.0.2 or later using your deployment method (e.g., pip install apache-superset==4.0.2, docker, or package manager)
  2. After upgrading, verify the installation by checking the Superset version in the UI or via command line
  3. Optionally, for additional defense in depth, configure the DISALLOWED_SQL_FUNCTIONS setting in superset_config.py to include the mentioned functions (version, query_to_xml, inet_server_addr, inet_client_addr) and any other functions you wish to restrict

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

Fix this in Superset Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
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,840.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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