SupersetApplication · Apache
CVE-2021-44451
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 · uneditedApache Superset up to and including 1.3.2 allowed for registered database connections password leak for authenticated users. This information could be accessed in a non-trivial way. Users should upgrade to Apache Superset 1.4.0 or higher.
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 · moderate confidenceApache Superset up to version 1.3.2 contains an information disclosure vulnerability where authenticated users can access plaintext passwords for registered database connections through a non-trivial access method. This allows unauthorized credential exposure to users who should not have access to connection passwords.
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.3.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Apache Superset versionRun the command to display the Superset version (commonly 'superset version' or check the package metadata/pip show apache-superset)Affected if The installed version is 1.3.2 or any earlier version (versions <= 1.3.2 are affected)
-
Identify registered database connectionsAccess the Superset UI and navigate to Data > Databases, or query the metadata database for records in the databases tableAffected if Any database connections are registered - the vulnerability exposes credentials for these connections
-
Verify if non-admin users have access to connection credentialsAs a non-administrator authenticated user, attempt to access the database connection configuration endpoint or UI page where connection details are displayedAffected if Non-admin users can view plaintext passwords in database connection settings - the vulnerability allows this unauthorized access
-
Check authentication configurationReview Superset authentication settings and role-based access controls to confirm which user roles exist and their permissionsAffected if There are authenticated users with roles other than admin - these users could potentially exploit the vulnerability
You are affected if your Apache Superset version is 1.3.2 or earlier and you have database connections configured with non-admin authenticated users present in the environment.
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 1.4.0 or higher to remediate the password leak vulnerability.
Apache Superset 1.4.0 or higher
- Back up your current Superset configuration and database
- Stop the Superset service
- Upgrade Apache Superset to version 1.4.0 or higher using your package manager (e.g., pip install apache-superset==1.4.0 or helm upgrade for Kubernetes deployments)
- Run database migrations if required (superset db upgrade)
- Restart the Superset service
- Verify the upgrade was successful and test that the credential leak vulnerability is fixed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Superset
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-44451 — 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-2021-44451 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