CVE-2018-15665
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 issue was discovered in Cloudera Data Science Workbench (CDSW) 1.2.x through 1.4.0. Unauthenticated users can get a list of user accounts.
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 confidenceCloudera Data Science Workbench (CDSW) versions 1.2.x through 1.4.0 expose an API endpoint that returns a list of user accounts without requiring authentication. This information disclosure vulnerability allows unauthenticated attackers to enumerate valid usernames, which aids in reconnaissance for targeted 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>= 1.2.0, <= 1.4.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Identify CDSW installation and versionCheck the installed version of Cloudera Data Science Workbench by querying the CDSW web interface version information, or use the 'cdsw version' command if you have CLI access to the CDSW host.Affected if The installed version is between 1.2.0 and 1.4.0 inclusive.
-
Confirm CDSW is network accessibleVerify that the Cloudera Data Science Workbench web interface is reachable over the network from an untrusted location, typically on port 80 or 443.Affected if CDSW is exposed to networks where untrusted users can initiate HTTP/HTTPS connections.
-
Test unauthenticated user enumeration endpointSend an unauthenticated HTTP GET request to the CDSW API endpoint that should list users. This is typically accessed at a path like /api/v1/users or similar API endpoint without providing any authentication credentials.Affected if The endpoint returns HTTP 200 with a list of user accounts or user data without requiring any authentication tokens or credentials.
-
Verify user list disclosureExamine the response from the unauthenticated API call. If the response contains JSON or other data structures showing valid usernames, email addresses, or user identifiers, the vulnerability is present.Affected if The response includes usernames or user account details that should only be visible to authenticated users.
You are affected if CDSW version is between 1.2.0 and 1.4.0 AND the user enumeration API endpoint responds to unauthenticated requests with user account information.
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 CDSW to a version newer than 1.4.0, or apply vendor-supplied patches. If upgrading is not immediately feasible, review network access controls to limit exposure of the CDSW interface to untrusted networks.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15665 — 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-2018-15665 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