CVE-2016-6353
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 · uneditedCloudera Search in CDH before 5.7.0 allows unauthorized document access because Solr Queries by document id can bypass Sentry document-level security via the RealTimeGetHandler.
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 Search in CDH before 5.7.0 contains a flaw where the Solr RealTimeGetHandler allows queries by document ID to bypass Sentry's document-level access controls, enabling unauthorized users to access documents they should not have permission to view.
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.0.0, < 5.7.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
- 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 CDH versionRun 'hadoop version' or check Cloudera Manager for the CDH version. Alternatively, check /etc/cloudera-scm-server/cmf.properties for the CDH parcel version.Affected if Version is >= 5.0.0 and < 5.7.0
-
Verify Cloudera Search (Solr) is deployedCheck if Solr service exists in Cloudera Manager under the cluster, or run 'solr --version' on the node if Solr client is installed.Affected if Solr service is running as part of the CDH cluster
-
Confirm RealTimeGetHandler is accessibleAttempt to access the Solr RealTimeGetHandler endpoint: http://<solr-host>:8983/solr/<collection>/get?id=<doc-id>. Check if the endpoint responds without authentication or returns document data.Affected if The RealTimeGetHandler responds to requests and returns document data without proper authorization checks
-
Check Sentry policy configuration for Solr collectionsReview Sentry policies for Solr: in Cloudera Manager, go to Sentry service > Configuration and inspect the Sentry policy files (sentry-site.xml). Look for any policies explicitly granting or denying access to the 'get' handler.Affected if Sentry policies do not explicitly cover or restrict the RealTimeGetHandler endpoint, or policies are missing for document-level access control on the get handler
A user is affected if their CDH version is between 5.0.0 and 5.7.0, they have Cloudera Search (Solr) deployed, the RealTimeGetHandler is accessible, and Sentry policies do not properly restrict document ID queries via that handler.
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.7.0
Upgrade to CDH 5.7.0 or later which contains the fix, or if immediate upgrade is not feasible, review and restrict access to the RealTimeGetHandler endpoint and verify Sentry policies are correctly applied to all Solr query paths.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6353 — 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-2016-6353 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