# CVE-2018-8003: Path traversal in Apache Ambari

> Unauthenticated attackers can read arbitrary files on the Ambari Server host via directory traversal, exposing sensitive data.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-hpj4-w9fj-7vgh

## What is CVE-2018-8003?

CVE-2018-8003 is a medium-severity path traversal vulnerability in Apache Ambari, published on 3 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Apache Ambari, versions 1.4.0 to 2.6.1, is susceptible to a directory traversal attack allowing an unauthenticated user to craft an HTTP request which provides read-only access to any file on the filesystem of the host the Ambari Server runs on that is accessible by the user the Ambari Server is running as. Direct network access to the Ambari Server is required to issue this request, and those Ambari Servers that are protected behind a firewall, or in a restricted network zone are at less risk of being affected by this issue.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Apache Ambari.

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

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

## Is CVE-2018-8003 being exploited?

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

## Other vulnerabilities in Apache Ambari

- [CVE-2017-5642](https://insights.sbomify.com/CVE-2017-5642/): Misconfiguration in Apache Ambari (critical 9.8)
- [CVE-2014-3582](https://insights.sbomify.com/CVE-2014-3582/): Command injection in n/a (critical 9.8)
- [CVE-2016-6807](https://insights.sbomify.com/CVE-2016-6807/): Apache Ambari Improper Access Control (critical 9.8)
- [CVE-2024-51941](https://insights.sbomify.com/CVE-2024-51941/): Apache Ambari: Remote Code Injection in Ambari Metrics and AMS Alerts (high 8.8)
- [CVE-2025-23196](https://insights.sbomify.com/CVE-2025-23196/): Apache Ambari: Code Injection Vulnerability in Ambari Alert Definition (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-8003 is a medium-severity path traversal vulnerability in Apache Ambari, published on 3 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-8003 in the wild and no public exploit code.

Affected product: Apache Ambari. 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-8003/ (Markdown: https://insights.sbomify.com/CVE-2018-8003/index.md)
```

## Sources

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

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