SupersetApplication · Apache
CVE-2022-43721
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, users could be redirected to this site when clicking on that specific dataset. This issue affects Apache Superset version 1.5.2 and prior versions and version 2.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 confidenceApache Superset versions 1.5.2 and prior and version 2.0.0 contain an open redirect vulnerability in the dataset link feature. An authenticated attacker with update datasets permission can modify a dataset's link URL to point to an arbitrary external site, causing users who click on that dataset to be redirected to the attacker-controlled site.
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.5.2= 2.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.
-
Identify Apache Superset versionCheck the installed Superset version via package manager, docker image tag, or by accessing the /health endpoint or version info in the UIAffected if The installed version is 1.5.2 or lower, or exactly 2.0.0
-
Verify update datasets permission existsIn Superset admin panel, navigate to Security -> List Roles and inspect which roles have the 'update datasets' or 'can edit' dataset permission grantedAffected if Any role beyond trusted administrators has update datasets permission enabled
-
Inspect dataset link configurationsQuery the datasets table or use the Superset UI to review the 'link' or 'external_link' field across all datasets. Look for entries containing URLs with domains different from your organization's domainAffected if Any dataset contains an external/external URL in its link field pointing to an untrusted domain
You are affected if running Superset 1.5.2 or lower, or version 2.0.0, and any user with update datasets permission has configured external URLs in dataset links that could redirect users to attacker-controlled sites.
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 · scopedUpgrade to a patched Apache Superset version that implements URL allowlist validation or prohibits external redirects in dataset links. Until then, restrict the 'update datasets' permission to highly trusted users only and monitor for suspicious dataset link modifications.
2.0.1
- 1. Back up your current Superset database and configuration.
- 2. Stop the Superset application services.
- 3. Upgrade Apache Superset to version 2.0.1 or later using your package manager (pip install apache-superset==2.0.1 or equivalent).
- 4. Run database migrations if required: superset db upgrade.
- 5. Restart Superset services.
- 6. Verify the upgrade by logging in and confirming dataset links function correctly.
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 / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43721 — 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-43721 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