dbcve.org
SupersetApplication · Apache

CVE-2019-12414

MEDIUM · 5.3 CVSS v3.1 Published 2019-12-16
Fix available
A fix is available. Upgrade to 0.32 or later.
See remediation →
62/100
Remediation priority · Elevated
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
In Apache Incubator Superset before 0.32, a user can view database names that he has no access to on a dropdown list in SQLLab

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 · moderate confidence

This is an information disclosure vulnerability in Apache Superset's SQLLab where the database dropdown list displays database names to users who do not have access permissions to those databases. The application fails to properly filter the database list based on the user's access control permissions before rendering it in the UI.

MitigationUpgrade to Apache Superset version 0.32 or later, which contains the fix for this authorization bypass in the SQLLab database dropdown.

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:< 0.32

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Apache Superset version
    Run 'pip show apache-superset' or check the package version in your installation. Alternatively, access the Superset UI and check the version information in the footer or about page.
    Affected if The installed version is less than 0.32 (e.g., 0.31.x, 0.30.x, etc.)
  2. Verify SQLLab access
    Log into Superset with a user account that has limited database permissions. Navigate to SQLLab (usually /sqllab endpoint) and examine the database dropdown selector above the query editor.
    Affected if The database dropdown displays database names that the logged-in user has NOT been explicitly granted access to in the permissions settings
  3. Cross-check user permissions
    As an administrator, review the user's actual permission grants in the Security menu. Confirm which databases the user should be able to see, then compare against what appears in the SQLLab dropdown.
    Affected if The visible databases in the dropdown exceed the databases the user is authorized to access per the permission configuration

A user is affected if running Apache Superset version 0.31 or earlier and can view databases they don't have permission to access in the SQLLab database dropdown.

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.

From vendor data
Upgrade available Upgrade to 0.32 or later
Fixed in 0.32
Interim mitigation

Upgrade to Apache Superset version 0.32 or later, which contains the fix for this authorization bypass in the SQLLab database dropdown.

Fix this in Superset Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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