# CVE-2017-9000: Path traversal in ArubaOS

> Unauthenticated attackers can access arbitrary files on Aruba mobility controllers via ports 8080/8081, potentially exposing sensitive credentials and leading to system compromise.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rx65-35rg-w842

## What is CVE-2017-9000?

CVE-2017-9000 is a critical path traversal vulnerability in Hewlett Packard Enterprise ArubaOS, published on 6 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ArubaOS, all versions prior to 6.3.1.25, 6.4 prior to 6.4.4.16, 6.5.x prior to 6.5.1.9, 6.5.2, 6.5.3 prior to 6.5.3.3, 6.5.4 prior to 6.5.4.2, 8.x prior to 8.1.0.4 FIPS and non-FIPS versions of software are both affected equally is vulnerable to unauthenticated arbitrary file access. An unauthenticated user with network access to an Aruba mobility controller on TCP port 8080 or 8081 may be able to access arbitrary files stored on the mobility controller. Ports 8080 and 8081 are used for captive portal functionality and are listening, by default, on all IP interfaces of the mobility controller, including captive portal interfaces. The attacker could access files which could contain passwords, keys, and other sensitive information that could lead to full system compromise.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Hp Arubaos.

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

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

## Is CVE-2017-9000 being exploited?

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

## Other vulnerabilities in Hewlett Packard Enterprise ArubaOS

- [CVE-2023-22779](https://insights.sbomify.com/CVE-2023-22779/): Unauthenticated Buffer Overflow Vulnerabilities in Services Accessed by the PAPI Protocol (critical 9.8)
- [CVE-2023-22780](https://insights.sbomify.com/CVE-2023-22780/): Unauthenticated Buffer Overflow Vulnerabilities in Services Accessed by the PAPI Protocol (critical 9.8)
- [CVE-2023-22781](https://insights.sbomify.com/CVE-2023-22781/): Unauthenticated Buffer Overflow Vulnerabilities in Services Accessed by the PAPI Protocol (critical 9.8)
- [CVE-2023-22782](https://insights.sbomify.com/CVE-2023-22782/): Unauthenticated Buffer Overflow Vulnerabilities in Services Accessed by the PAPI Protocol (critical 9.8)
- [CVE-2023-22783](https://insights.sbomify.com/CVE-2023-22783/): Unauthenticated Buffer Overflow Vulnerabilities in Services Accessed by the PAPI Protocol (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-9000 is a critical path traversal vulnerability in Hewlett Packard Enterprise ArubaOS, published on 6 Aug 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-2017-9000 in the wild and no public exploit code.

Affected product: Hewlett Packard Enterprise ArubaOS. 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-9000/ (Markdown: https://insights.sbomify.com/CVE-2017-9000/index.md)
```

## Sources

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

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