# CVE-2016-6353: Missing authorization in n/a

> Attackers can bypass Sentry document-level security to access unauthorized documents via Solr RealTimeGetHandler in Cloudera Search.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Nov 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xfq9-m5c5-8p4q

## What is CVE-2016-6353?

CVE-2016-6353 is a medium-severity missing authorization vulnerability in n/a, published on 26 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cloudera 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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2016-6353?

It affects 1 product.


Products: Cloudera Cdh.

## How do I fix CVE-2016-6353?

No fix has been published for CVE-2016-6353 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-6353 being exploited?

There is no known exploitation of CVE-2016-6353 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2015-7831](https://insights.sbomify.com/CVE-2015-7831/): In Cloudera Hue, there is privilege escalation by a read-only user when CDH 5.x brefore 5.4.9 is used. (high 8.8)
- [CVE-2016-4572](https://insights.sbomify.com/CVE-2016-4572/): Missing authorization in n/a (high 8.8)
- [CVE-2019-7319](https://insights.sbomify.com/CVE-2019-7319/): Privilege escalation in n/a (high 8.3)
- [CVE-2016-5724](https://insights.sbomify.com/CVE-2016-5724/): Information disclosure in n/a (high 7.5)
- [CVE-2017-9325](https://insights.sbomify.com/CVE-2017-9325/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6353 and fix it if it is affected.

What it is: CVE-2016-6353 is a medium-severity missing authorization vulnerability in n/a, published on 26 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-6353 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-6353/ (Markdown: https://insights.sbomify.com/CVE-2016-6353/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-6353
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-6353
- OSV: https://osv.dev/vulnerability/CVE-2016-6353

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-6353/
Summaries are generated and may contain mistakes; the official description above is the record.