# CVE-2017-7399: Privilege escalation in n/a

> A read-only user can discover other usernames and elevate their privileges, requiring an upgrade to Cloudera Manager.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 5 Aug 2024
- **Also known as:** GHSA-2jx7-jqgc-hgxg

## What is CVE-2017-7399?

CVE-2017-7399 is a high-severity 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 Manager 5.8.x before 5.8.5, 5.9.x before 5.9.2, and 5.10.x before 5.10.1 allows a read-only Cloudera Manager user to discover the usernames of other users and elevate the privileges of those users.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2017-7399?

It affects 1 product.


Products: Cloudera Cloudera Manager.

## How do I fix CVE-2017-7399?

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

## Is CVE-2017-7399 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-30132](https://insights.sbomify.com/CVE-2021-30132/): Privilege escalation in n/a (critical 9.8)
- [CVE-2018-11744](https://insights.sbomify.com/CVE-2018-11744/): Missing authorization in n/a (high 8.1)
- [CVE-2015-6495](https://insights.sbomify.com/CVE-2015-6495/): Information disclosure in n/a (high 7.5)
- [CVE-2017-9326](https://insights.sbomify.com/CVE-2017-9326/): Information disclosure in n/a (high 7.5)
- [CVE-2016-3192](https://insights.sbomify.com/CVE-2016-3192/): Information disclosure in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-7399 and fix it if it is affected.

What it is: CVE-2017-7399 is a high-severity 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-2017-7399 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-2017-7399/ (Markdown: https://insights.sbomify.com/CVE-2017-7399/index.md)
```

## Sources

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

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