CVE-2019-12413
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 · uneditedIn Apache Incubator Superset before 0.31 user could query database metadata information from a database he has no access to, by using a specially crafted complex query.
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 before version 0.31 contains an authorization bypass vulnerability in its database metadata query functionality. Users can access metadata information from databases they have not been granted access to by crafting specially designed complex queries that exploit insufficient access control checks in the metadata exploration features.
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< 0.31CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Apache Superset versionRun the command to check the Superset version, such as via pip show apache-superset, checking the version in package metadata, or querying the Superset metadata database for the version informationAffected if The installed version is lower than 0.31 (e.g., 0.30.x, 0.29.x, or earlier)
-
Identify if metadata exploration features are accessibleVerify whether the Superset instance has the metadata exploration or database exploration features enabled. Check the Superset configuration for feature flags related to metadata querying or database explorationAffected if Metadata exploration features are enabled and accessible to users without additional authentication barriers
-
Check user database access control assignmentsReview the access control configurations in Superset to determine which users have been explicitly granted access to which databases. Examine the permission model for database metadata accessAffected if Users exist who have limited or no explicit database access permissions, yet the metadata exploration feature can be accessed by them
-
Verify metadata exposure through complex queriesAs a test with a low-privilege user who has no access to certain databases, attempt to craft complex metadata exploration queries (such as querying database metadata endpoints) to see if information from unauthorized databases can be retrievedAffected if A user without access to a specific database can retrieve metadata information about that database through complex queries
A Superset instance is affected if it runs version lower than 0.31, has metadata exploration features enabled, and allows users to access metadata from databases they have not been explicitly granted permission to access.
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.
From vendor data0.31
Upgrade to Apache Superset version 0.31 or later, which contains the proper access control enforcement fixes for this metadata information disclosure vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12413 — 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-2019-12413 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