dbcve.org
SupersetApplication · Apache

CVE-2023-49734

MEDIUM · 6.5 CVSS v3.1 Published 2023-12-19
Fix available
A fix is available. Upgrade to 2.1.2 / 3.0.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
An authenticated Gamma user has the ability to create a dashboard and add charts to it, this user would automatically become one of the owners of the charts allowing him to incorrectly have write permissions to these charts.This issue affects Apache Superset: before 2.1.2, from 3.0.0 before 3.0.2. Users are recommended to upgrade to version 3.0.2 or 2.1.3, which fixes the 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 · high confidence

An authenticated Gamma user in Apache Superset can create a dashboard and add existing charts to it, which automatically grants them ownership of those charts. This allows users with read-only Gamma role permissions to incorrectly gain write permissions to charts they should not be able to modify.

MitigationUpgrade Apache Superset to version 3.0.2 or 2.1.3 which fixes the authorization flaw where dashboard creators automatically become chart owners.

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
Affected:< 2.1.2>= 3.0.0, < 3.0.2

CVSS 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
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify your Apache Superset version
    Check the version file or API endpoint (e.g., /api/v1/version) to confirm the installed version of Apache Superset
    Affected if The installed version is < 2.1.2 OR >= 3.0.0 and < 3.0.2
  2. Verify if Gamma role users exist
    Query the Superset database or use the users API to list users with the Gamma role assigned
    Affected if There are users assigned the Gamma (read-only) role in the system
  3. Identify dashboards created by Gamma users
    Query the dashboards table/database to list dashboards where the created_by field corresponds to a Gamma role user
    Affected if Gamma role users have created any dashboards in the system
  4. Check for unintended chart ownership
    Query the charts table/database to identify charts where the owner_id corresponds to a user who should only have Gamma (read-only) permissions
    Affected if Any chart shows ownership by a user whose primary role is Gamma (read-only), indicating they incorrectly gained write access through dashboard creation
  5. Audit chart modification history
    Review the chart audit logs or history to confirm if Gamma users have performed write operations (edit, update) on charts they should not have access to
    Affected if Gamma users have modified charts they should not have been able to write to, confirming active exploitation

You are affected if your Apache Superset version falls within the vulnerable range (< 2.1.2 or >= 3.0.0 and < 3.0.2) AND Gamma role users have created dashboards and subsequently gained ownership of charts they should only be able to read.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.1.2 / 3.0.2 or later
Fixed in 2.1.23.0.2
Interim mitigation

Upgrade Apache Superset to version 3.0.2 or 2.1.3 which fixes the authorization flaw where dashboard creators automatically become chart owners.

Recommended fix High confidence

3.0.2 or 2.1.3

  1. 1. Back up your current Superset database and configuration.
  2. 2. Review the Apache Superset 3.0.2 or 2.1.3 release notes for any breaking changes or migration requirements.
  3. 3. Stop the Superset service.
  4. 4. Upgrade Superset using your package manager (e.g., pip install apache-superset==3.0.2 or pip install apache-superset==2.1.3).
  5. 5. Run any required database migrations (superset db upgrade).
  6. 6. Restart the Superset service.
  7. 7. Verify the fix by logging in as a Gamma user and confirming the authorization behavior is corrected.
Caveat Check release notes for version-specific breaking changes before upgrading

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-49734 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-49734 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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