dbcve.org
SupersetApplication · Apache

CVE-2023-30776

MEDIUM · 6.5 CVSS v3.1 Published 2023-04-24
Fix available
A fix is available. Upgrade to after 2.0.1 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 user with specific data permissions could access database connections stored passwords by requesting a specific REST API. This issue affects Apache Superset version 1.3.0 up to 2.0.1.

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

Authenticated users with specific data permissions in Apache Superset versions 1.3.0 through 2.0.1 can retrieve stored database connection passwords by calling a specific REST API endpoint, exposing sensitive credentials.

MitigationUpgrade Apache Superset to version 2.0.1 or later. Review user permissions and audit access logs for unauthorized password retrieval attempts.

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:>= 1.3.0, <= 2.0.1

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installed Superset version
    Run the command 'superset version' or check the package.json/pom.xml file in your Superset installation directory, or query the /api/v1/version endpoint if accessible
    Affected if The version returned is >= 1.3.0 and <= 2.0.1
  2. Audit user roles with data permissions
    Access the Superset admin panel and review all roles assigned to users, specifically looking for permissions related to 'database access' or ' datasource access' under the 'Datasources' or 'Security' menus
    Affected if Any user role grants access to databases or datasources beyond what they should have
  3. Review API access logs for connection password retrieval attempts
    Check Superset logs (typically in /var/log/superset/ or the configured log directory) for requests to REST API endpoints that query database connections, looking for patterns like /api/v1/database/ or /api/v1/datasource/ with parameter variations
    Affected if Logs show API calls to database connection endpoints that retrieved password fields or sensitive connection details
  4. Verify REST API endpoint exposure
    If you have API access, test whether the GET /api/v1/database/{id} endpoint (or similar connection retrieval endpoints) returns password fields in the response payload
    Affected if The API returns password or connection_string fields in plain text in the response

You are affected if your Superset version is between 1.3.0 and 2.0.1 inclusive AND any user has permissions to access database connection information through the REST API.

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 a release after 2.0.1
Interim mitigation

Upgrade Apache Superset to version 2.0.1 or later. Review user permissions and audit access logs for unauthorized password retrieval attempts.

Recommended fix Moderate confidence

2.1.0 or later

  1. Upgrade Apache Superset to version 2.1.0 or later
  2. Verify that the REST API endpoint `/api/v1/database/{id}` no longer returns plaintext passwords in the response
  3. Review user permissions to ensure only authorized users can access database connection details
  4. After upgrade, confirm database connections still function correctly
Caveat Review the 2.1.0 release notes for any breaking changes, particularly around database connection handling and API changes

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
10.0 hours of engineering $1,720
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-30776 — 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-30776 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