SupersetApplication · Apache
CVE-2020-1932
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 · uneditedAn information disclosure issue was found in Apache Superset 0.34.0, 0.34.1, 0.35.0, and 0.35.1. Authenticated Apache Superset users are able to retrieve other users' information, including hashed passwords, by accessing an unused and undocumented API endpoint on Apache Superset.
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 versions 0.34.0 through 0.35.1 contain an undocumented API endpoint that allows any authenticated user to query and retrieve other users' profile information, including their hashed passwords. This represents a broken access control vulnerability where proper authorization checks are not enforced on the endpoint.
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
= 0.34.0= 0.34.1= 0.35.0= 0.35.1CVSS 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.
-
Verify installed Apache Superset versionCheck the Superset version by accessing the /health endpoint, reviewing package.json, or running 'superset version' command if available. Compare against affected versions 0.34.0 through 0.35.1.Affected if The installed version is 0.34.0, 0.34.1, 0.35.0, or 0.35.1.
-
Identify undocumented API endpointReview Superset API routing configuration files (typically in superset/views/core.py or superset/api/v1.py) for any profile-related endpoints that are not documented in the official API. Look for endpoints handling user profile data beyond standard user info.Affected if An undocumented API endpoint exists that exposes user profile data.
-
Test cross-user profile accessLog in as a standard authenticated user (user A). Using a tool like curl or Postman, attempt to make an API request to profile endpoints using another user ID (user B). Observe if the response includes sensitive data such as password hashes or other users' private information.Affected if An authenticated user can retrieve another user's profile data including hashed passwords without proper authorization checks.
-
Inspect API response for password hash exposureMake API calls to user profile endpoints and examine the JSON response payload. Specifically check if the 'password' or 'password_hash' fields are returned in API responses to non-admin users.Affected if API responses include hashed passwords or sensitive credential information in the profile data.
You are affected if running Apache Superset version 0.34.0 through 0.35.1 and the undocumented API endpoint allows authenticated users to access other users' profile data including password hashes.
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.
From vendor dataUpgrade to Apache Superset version 0.36.0 or later, or remove/disable the undocumented endpoint and implement proper row-level authorization checks to ensure users can only access their own profile data.
Fix this in Superset
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1932 — 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-2020-1932 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