CVE-2018-10815
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 Manager before 5.13.4, 5.14.x before 5.14.4, and 5.15.x before 5.15.1. A read-only user can access sensitive cluster information.
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 confidenceA vulnerability in Cloudera Manager allows authenticated read-only users to bypass intended access controls and view sensitive cluster information that should be restricted to administrative users, exposing potentially confidential configuration data, credentials, or cluster metadata.
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< 5.13.4>= 5.14.0, < 5.14.4>= 5.15.0, < 5.15.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.0/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.
-
Identify Cloudera Manager versionLog into Cloudera Manager admin UI and navigate to Support > About, or run 'cloudera-manager --version' from the command line on the CM hostAffected if The displayed version falls outside the fixed releases: not 5.13.4+, not 5.14.4+, and not 5.15.1+ (i.e., < 5.13.4, or >= 5.14.0 and < 5.14.4, or >= 5.15.0 and < 5.15.1)
-
Confirm read-only user accounts existIn Cloudera Manager UI, go to Administration > Users and Roles and look for users assigned the 'Read Only' roleAffected if Any user account is assigned the Read Only role in a Cloudera Manager version that falls within the affected ranges above
-
Verify role-based access control configurationIn Cloudera Manager UI, navigate to Administration > Security > Authentication and review whether role-based access controls are enforced for API endpointsAffected if The access control settings allow read-only users to query administrative APIs or configuration endpoints that should be restricted to Admin role holders
-
Audit sensitive endpoint accessReview Cloudera Manager server logs (typically in /var/log/cloudera-scm-server/) for API calls made by users with read-only role to paths such as /api/v13/clusters/ or /api/v14/cm/deploymentAffected if Logs show read-only users successfully accessing endpoints that should return 403 Forbidden or require Admin role
A user is affected if their Cloudera Manager version is within the vulnerable ranges AND read-only user accounts exist and can access administrative or sensitive configuration data that should be restricted to admin users.
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 data5.13.45.14.45.15.1
Upgrade Cloudera Manager to version 5.13.4, 5.14.4, or 5.15.1 or later to patch the authorization bypass. Verify that read-only user accounts can no longer access sensitive cluster information after the upgrade.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10815 — 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-10815 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