Security readout for executives and security teams
Plain-English summary
Some CDH deployments allowed users to retrieve protected search documents if they knew a document ID. This bypassed Sentry document-level security in Cloudera Search through Solr's RealTimeGetHandler. The issue matters most where search indexes contain sensitive data and access decisions depend on Sentry filtering.
Executive priority
Prioritize remediation where Cloudera Search indexes confidential data and Sentry is relied on for access control. The available public record lacks CVSS and exploitation evidence, so urgency depends on data sensitivity and exposure of the search service.
Technical view
Cloudera Search in CDH before 5.7.0 could allow unauthorized document access. Solr queries by document ID through RealTimeGetHandler could bypass Sentry document-level security controls. The source bundle does not provide CVSS, CWE, exploit details, or broad product/version metadata beyond CDH before 5.7.0.
Likely exposure
Exposure appears limited to organizations running Cloudera Search in CDH before 5.7.0, especially where Sentry document-level security protects documents in Solr indexes.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. The vulnerability requires an affected deployment and likely depends on access to query Cloudera Search/Solr document retrieval functionality.
Researcher notes
The core issue is an authorization bypass path: RealTimeGetHandler document-ID retrieval could avoid Sentry document-level filtering. Public source detail is sparse; avoid assuming exploit mechanics, prerequisites, or fixed code behavior beyond the affected-version statement.
Mitigation direction
- Upgrade affected CDH Cloudera Search deployments to 5.7.0 or later per Cloudera guidance.
- Review Cloudera security bulletin TSB-165 for vendor-confirmed remediation details.
- Limit Solr/Cloudera Search access to trusted users and networks while remediation is planned.
- Audit search indexes that rely on Sentry document-level security for sensitive content.
Validation and detection
- Inventory CDH versions and identify Cloudera Search deployments before 5.7.0.
- Confirm whether Sentry document-level security is used for Solr-indexed documents.
- Review access logs for unexpected document-ID retrieval patterns where available.
- Verify upgraded systems no longer match the affected version range.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2016-6353 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://docs.cloudera.com/documentation/other/security-bulletins/topics/Security-Bulletin.html#tsb_165CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.