SupersetApplication · Apache
CVE-2024-55633
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 · uneditedImproper Authorization vulnerability in Apache Superset. On Postgres analytic databases an attacker with SQLLab access can craft a specially designed SQL DML statement that is Incorrectly identified as a read-only query, enabling its execution. Non postgres analytics database connections and postgres analytics database connections set with a readonly user (advised) are not vulnerable. This issue affects Apache Superset: before 4.1.0. Users are recommended to upgrade to version 4.1.0, 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 confidenceApache Superset before 4.1.0 contains an improper authorization flaw where SQLLab incorrectly identifies certain Postgres DML statements as read-only queries. An attacker with SQLLab access can craft specially designed INSERT, UPDATE, or DELETE statements that bypass the read-only check, allowing unauthorized data modification on Postgres analytic database connections.
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
< 4.1.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check Apache Superset versionRun 'pip show apache-superset' or check the version in your package manager to determine if the installed version is before 4.1.0Affected if Installed version is less than 4.1.0
-
Verify SQLLab is enabledCheck Superset configuration file (superset_config.py) for ENABLE_SQLLAB = True, or inspect the Superset UI to confirm SQLLab feature is accessible to usersAffected if SQLLab is enabled and accessible to the user in question
-
Identify Postgres analytic database connectionsIn Superset UI, navigate to Data > Databases, or query the 'dbs' table in the metadata database to list all configured database connectionsAffected if Any database connection uses Postgres as the engine type (postgresql)
-
Check database user privileges on Postgres connectionsReview the connection configuration for each Postgres database to determine if the database user is configured as read-only or has only SELECT privilegesAffected if The Postgres connection uses a database user with write privileges (INSERT, UPDATE, DELETE) rather than a read-only user
You are affected if running Apache Superset version below 4.1.0, SQLLab is enabled, and you have Postgres database connections that do not use a read-only database user.
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 · scoped4.1.0
Upgrade Apache Superset to version 4.1.0 or later, or ensure Postgres analytic database connections use a readonly database user to prevent exploitation.
4.1.0
- Upgrade Apache Superset to version 4.1.0 or later as recommended in the official security advisory
- Verify the upgrade was successful by checking the Superset version
- For additional defense-in-depth with Postgres analytic databases, configure the connection to use a readonly database user as advised in the advisory
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
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-55633 — 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-2024-55633 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