CVE-2019-12413 json
Users able to query database metadata in Apache Superset
published 6y ago modified 4mo ago also GHSA-p5w7-qmq6-pmjr , PYSEC-2019-172 , EUVD-2019-0018
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.8%
- EPSS 2.8% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
In 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.
Patch / fix
- pypi apache-superset 0.31, 0.31.0
- apache superset 0.31
Is CVE-2019-12413 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
2.80% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | apache-superset | <0.31.0 <0.31 |
0.31.0 0.31 |
Affected products
- n/a Apache Incubator Superset
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
lists.apache.org
/thread.html/85ab04f8c52df8c353ecfa0ecd2ff27fc07fb8ab7566a754349806be%40%3Cdev.superset.apache.org%3E
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-12413
advisory
-
github.com
/apache/superset
package
-
github.com
/pypa/advisory-database/tree/main/vulns/apache-superset/PYSEC-2019-172.yaml
web
-
snyk.io
/vuln/SNYK-PYTHON-APACHESUPERSET-558911
web
-
github.com
/advisories/GHSA-p5w7-qmq6-pmjr
advisory
Sources
- CVE List CVE-2019-12413
- GitHub Advisory GHSA-p5w7-qmq6-pmjr
- NVD CVE-2019-12413
- OSV PYSEC-2019-172
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.