dbcve.org
SupersetApplication · Apache

CVE-2024-34693

MEDIUM · 5.3 CVSS v3.1 Published 2024-06-20
Fix available
A fix is available. Upgrade to 3.1.3 / 4.0.1 or later.
See remediation →
59/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 Input Validation vulnerability in Apache Superset, allows for an authenticated attacker to create a MariaDB connection with local_infile enabled. If both the MariaDB server (off by default) and the local mysql client on the web server are set to allow for local infile, it's possible for the attacker to execute a specific MySQL/MariaDB SQL command that is able to read files from the server and insert their content on a MariaDB database table.This issue affects Apache Superset: before 3.1.3 and version 4.0.0 Users are recommended to upgrade to version 4.0.1 or 3.1.3, 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

Improper input validation in Apache Superset allows authenticated users to create MariaDB connections with local_infile enabled. When both the MariaDB server and local mysql client permit local infile (both off by default), an attacker can execute specific MySQL/MariaDB SQL commands to read files from the server filesystem and insert their contents into a database table.

MitigationUpgrade Apache Superset to version 3.1.3 or 4.0.1 to remediate this vulnerability. Additionally, ensure local_infile is disabled on MariaDB servers and the local mysql client unless explicitly required.

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.1.3>= 4.0.0, < 4.0.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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/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. Check installed Apache Superset version
    Run `pip show apache-superset` or check the version in your package manager to get the exact version number installed in your environment
    Affected if The installed version is less than 3.1.3, or greater than or equal to 4.0.0 but less than 4.0.1
  2. Identify MariaDB database connections in Superset
    Query the Superset metadata database for connections with database type 'mysql' or 'mariadb', or use the Superset UI to list all database connections and identify those using MariaDB
    Affected if There exists at least one active MariaDB or MySQL connection configured in Superset
  3. Check if local_infile is enabled on MariaDB connections
    Examine the database connection parameters in Superset metadata DB (table 'dbs' or similar) or inspect the connection configuration in the UI to see if local_infile is set to 1 or enabled
    Affected if local_infile is explicitly enabled (set to 1, true, or yes) in any MariaDB database connection configuration

You are affected if you are running an affected Superset version AND have a MariaDB connection with local_infile enabled, because the vulnerability allows authenticated users to enable local_infile (which should be restricted) and read files from the database server filesystem.

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.1.3 / 4.0.1 or later
Fixed in 3.1.34.0.1
Interim mitigation

Upgrade Apache Superset to version 3.1.3 or 4.0.1 to remediate this vulnerability. Additionally, ensure local_infile is disabled on MariaDB servers and the local mysql client unless explicitly required.

Recommended fix High confidence

3.1.3 or 4.0.1

  1. Ensure you have a backup of your Superset database and configuration
  2. Stop the Superset application services
  3. Consult the official Apache Superset upgrade documentation for your deployment method
  4. Upgrade to version 3.1.3 or version 4.0.1 depending on your target release line
  5. Verify the upgrade by checking the Superset version in the UI or via command line
  6. Test that MariaDB connections work properly after upgrade
  7. Restart Superset services

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

Fix this in Superset Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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