SupersetApplication · Apache
CVE-2023-36388
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 REST API permission in Apache Superset up to and including 2.1.0 allows for an authenticated Gamma users to test network connections, possible SSRF.
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 confidenceImproper authorization in Apache Superset's REST API allows authenticated Gamma (low-privilege) users to access network connection testing functionality that should be restricted to higher-privileged roles, enabling potential Server-Side Request Forgery (SSRF) attacks.
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
<= 2.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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 command: pip show apache-superset or check package.json/version file in the Superset installation directory. Alternatively, access the Superset UI and check the version info in the welcome/about section.Affected if Version is 2.1.0 or lower
-
Confirm Gamma role exists in the systemAccess Superset administration panel, navigate to Security > List Roles, or query the ab_role table in the metadata database to verify the existence of the Gamma role.Affected if Gamma role is present and assigned to any users
-
Verify if network connection testing API is accessible to Gamma usersAs a Gamma user, attempt to access the database connection test endpoint (typically POST /api/v1/database/{id}/test_connection or similar REST API endpoint for testing database connections). Check if the request succeeds without 403 Forbidden response.Affected if Gamma users can successfully make requests to connection testing endpoints without receiving authorization errors
-
Check Gamma user permissions for connection-related featuresNavigate to Security > List Roles > Gamma > View Permissions, or query the permission tables in the metadata database to list all permissions assigned to Gamma role. Look for database connection test, test connection, or similar permissions.Affected if Gamma role has permissions for database connection testing or test_connection actions
A user is affected if running Apache Superset version 2.1.0 or lower AND has Gamma role users who can access the database connection testing REST API endpoints.
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 version 2.1.1 or later which contains the fix for this improper permission enforcement issue.
Superset 2.1.1 or later (latest stable release)
- 1. Back up your current Superset installation and database.
- 2. Review the release notes for Superset 2.1.1 and later versions to confirm SSRF fix inclusion.
- 3. Upgrade Apache Superset to version 2.1.1 or later (recommended: latest stable release).
- 4. Verify the upgrade was successful and test that Gamma users no longer have network connection testing capabilities.
- 5. Confirm the fix by checking that the vulnerable API endpoint now properly restricts Gamma role users.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Superset
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-36388 — 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-36388 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