SupersetApplication · Apache
CVE-2022-27479
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 · uneditedApache Superset before 1.4.2 is vulnerable to SQL injection in chart data requests. Users should update to 1.4.2 or higher which addresses this 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 · moderate confidenceApache Superset before version 1.4.2 contains a SQL injection vulnerability in chart data request endpoints, allowing attackers to manipulate database queries through specially crafted requests. The critical CVSS score of 9.8 indicates this vulnerability can be exploited without authentication.
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
< 1.4.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Apache Superset versionRun the command 'superset version' or check the package version via pip list (pip show apache-superset) or check the VERSION_INFO file in the Superset installation directoryAffected if The reported version is below 1.4.2 (e.g., 1.4.1, 1.4.0, 1.3.x, etc.)
-
Verify chart data endpoints are accessibleConfirm that the Superset web interface or API endpoints for chart data are exposed and operational. These endpoints typically follow patterns like /api/v1/chart/data or /superset/explore_json/Affected if Chart data endpoints are reachable (by default they are accessible without authentication in unpatched versions)
-
Check if authentication is enforced on API endpointsReview the Superset configuration file (superset_config.py) for API authentication settings. Test accessing chart data API endpoints without providing credentialsAffected if Chart data endpoints can be accessed without authentication (the vulnerability is exploitable pre-authentication)
If Apache Superset version is below 1.4.2 and chart data endpoints are accessible without authentication, the environment is vulnerable to CVE-2022-27479.
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.
dbcve · scoped1.4.2
Upgrade Apache Superset to version 1.4.2 or higher to remediate this SQL injection vulnerability in chart data requests.
1.4.2 or latest stable release
- 1. Back up your current Superset installation and database
- 2. Upgrade Apache Superset to version 1.4.2 or higher
- 3. Verify the upgrade was successful by logging into Superset
- 4. Test that chart data requests function correctly
- 5. Review Superset logs to confirm no SQL injection errors occur
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Superset
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing8.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 $4,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27479 — 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-2022-27479 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