SupersetApplication · Apache
CVE-2023-42502
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 · uneditedAn authenticated attacker with update datasets permission could change a dataset link to an untrusted site by spoofing the HTTP Host header, users could be redirected to this site when clicking on that specific dataset. This issue affects Apache Superset versions before 3.0.0.
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 confidenceAn authenticated attacker with 'update datasets' permission can perform HTTP Host header poisoning to change dataset links to point to untrusted external sites. When users click on these manipulated dataset links, they get redirected to the attacker's controlled site, enabling phishing or malware delivery.
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
< 3.0.0CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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.
-
Check Apache Superset versionRun the command to retrieve the installed Superset version (e.g., 'superset version', check package.json, or query the metadata database)Affected if The installed version is lower than 3.0.0
-
Verify if update datasets permission existsCheck the Superset roles and permissions configuration (typically in the FAB database tables such as 'ab_role' and 'ab_permission') to determine if the 'update datasets' permission is defined and assigned to any rolesAffected if The 'update datasets' permission exists and is assigned to any user role
-
Identify users with update datasets permissionQuery the permission-to-role mappings (e.g., from the 'ab_role_permission_view' table) to list all users or roles that have the 'update datasets' permissionAffected if Any user account is granted the 'update datasets' permission
-
Inspect dataset configurations for external URLsExamine the dataset records in the Superset metadata database (typically in tables like 'datasources' or 'datasets') to identify any external_url or link fields that point to untrusted or unexpected domainsAffected if Any dataset contains an external URL pointing to a domain not in your organization's allowlist
-
Review recent dataset modificationsCheck dataset change logs or audit tables (if enabled) for recent updates to dataset link/URL fields, focusing on changes that introduce external URLsAffected if Recent dataset link modifications reference unfamiliar external domains
You are affected if your Superset version is below 3.0.0 and any user has the 'update datasets' permission, regardless of whether external URLs are currently present in datasets.
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 · scoped3.0.0
Upgrade to Apache Superset 3.0.0 or later. Implement strict allowlist-based validation of HTTP Host headers on the server side to reject unexpected values.
3.0.0
- Ensure you have a complete backup of your Superset database and configuration
- Review the Apache Superset 3.0.0 release notes for any breaking changes relevant to your deployment
- Upgrade your Superset installation to version 3.0.0 using your package manager or deployment method (e.g., pip install apache-superset==3.0.0 or equivalent)
- Restart all Superset services to load the new version
- Verify the upgrade was successful by logging in and checking the Superset version number
- Test that dataset links function correctly and no open redirect vulnerabilities remain
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
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-42502 — 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-2023-42502 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