# CVE-2018-15804: Privilege escalation in n/a

> Compromised MapR ticket credentials allow users to impersonate any other user, including cluster administrators, in the MapR Converged Data Platform.

- **Severity:** High 8.8 (`CVSS:3.0/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:** 23 Aug 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-6wgm-vmwq-hhq2

## What is CVE-2018-15804?

CVE-2018-15804 is a high-severity vulnerability in n/a, published on 23 Aug 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in the MapR File System in MapR Converged Data Platform and MapR-XD 6.x and earlier. Under certain conditions, it is possible for MapR ticket credentials to become compromised, allowing a user to escalate their privileges to act as (aka impersonate) any other user, including cluster administrators, aka bug# 31935. This affects all users who have enabled security on the MapR platform and is fixed in mapr-patch-5.2.1.42646.GA-20180731093831, mapr-patch-5.2.2.44680.GA-20180802011430, mapr-patch-6.0.0.20171109191718.GA-20180802011420, and mapr-patch-6.0.1.20180404222005.GA-20180806214919.

## Which versions are affected by CVE-2018-15804?

It affects 1 product.


Products: Mapr Mapr.

## How do I fix CVE-2018-15804?

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

## Is CVE-2018-15804 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-12017](https://insights.sbomify.com/CVE-2019-12017/): Deserialization in MapR-MFS/CLDB (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-15804 and fix it if it is affected.

What it is: CVE-2018-15804 is a high-severity vulnerability in n/a, published on 23 Aug 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-15804 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-2018-15804/ (Markdown: https://insights.sbomify.com/CVE-2018-15804/index.md)
```

## Sources

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

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