SupersetApplication · Apache
CVE-2022-43717
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 · uneditedDashboard rendering does not sufficiently sanitize the content of markdown components leading to possible XSS attack vectors that can be performed by authenticated users with create dashboard permissions. 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 dashboard markdown component fails to properly sanitize user-supplied content, allowing authenticated users with create dashboard permissions to inject malicious JavaScript code through markdown that executes when other users view the affected dashboard.
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 installed Apache Superset versionRun the command 'superset version' or check the version file in the Superset installation directory, typically found in the package metadataAffected if The version number is 1.5.2 or lower, or exactly 2.0.0
-
Verify dashboard creation permissions existAccess Superset admin panel, navigate to Security > List of Roles, and review which roles have the 'can write' or 'dashboard write' permission enabledAffected if Untrusted or non-admin users have dashboard creation or write permissions enabled
-
Examine dashboards for markdown componentsOpen the Superset UI, go to the Dashboards section, and inspect each dashboard for markdown visualization widgets or text boxesAffected if Any dashboards contain markdown-enabled components that could render user-supplied content
-
Review markdown content for potential script injectionView the raw markdown source of any dashboard markdown components, looking for HTML script tags, javascript: URIs, or onload/onerror event handlersAffected if The markdown content contains unsanitized HTML script tags or JavaScript event handlers that could execute malicious code
You are affected if your Apache Superset version is 1.5.2 or lower, or exactly 2.0.0, and untrusted users have dashboard creation permissions with dashboards containing markdown components.
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 Apache Superset to a version beyond 2.0.0 that includes proper markdown sanitization, or apply the vendor patch if available. Until then, restrict dashboard creation permissions to trusted users only.
Superset 2.0.1 or later
- 1. Back up your current Superset configuration and database
- 2. Stop the Superset service
- 3. Upgrade to Superset version 2.0.1 or later using your package manager (e.g., pip install apache-superset==2.0.1)
- 4. Run database migrations if required: superset db upgrade
- 5. Restart the Superset service
- 6. Verify the markdown component rendering works correctly and test that XSS payloads are now sanitized
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Superset
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43717 — 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-43717 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