# CVE-2017-9136: Path traversal in n/a

> An attacker can exploit an unsanitized GET parameter to download arbitrary files, including credentials and keys, leading to full administrative access.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 21 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9w6p-9j5m-6qr6

## What is CVE-2017-9136?

CVE-2017-9136 is a high-severity path traversal vulnerability in n/a, published on 21 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on Mimosa Client Radios before 2.2.3. In the device's web interface, there is a page that allows an attacker to use an unsanitized GET parameter to download files from the device as the root user. The attacker can download any file from the device's filesystem. This can be used to view unsalted, MD5-hashed administrator passwords, which can then be cracked, giving the attacker full admin access to the device's web interface. This vulnerability can also be used to view the plaintext pre-shared key (PSK) for encrypted wireless connections, or to view the device's serial number (which allows an attacker to factory reset the device).

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-522 (Insufficiently Protected Credentials), CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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

It affects 2 products.


Products: Mimosa Backhaul Radios, Mimosa Client Radios.

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

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

## Is CVE-2017-9136 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-9133](https://insights.sbomify.com/CVE-2017-9133/): Command injection in n/a (high 8.8)
- [CVE-2017-9135](https://insights.sbomify.com/CVE-2017-9135/): Command injection in n/a (high 8.8)
- [CVE-2017-9131](https://insights.sbomify.com/CVE-2017-9131/): Command injection in n/a (high 7.5)
- [CVE-2017-9132](https://insights.sbomify.com/CVE-2017-9132/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2017-9134](https://insights.sbomify.com/CVE-2017-9134/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-9136 is a high-severity path traversal vulnerability in n/a, published on 21 May 2017. 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-9136 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-9136/ (Markdown: https://insights.sbomify.com/CVE-2017-9136/index.md)
```

## Sources

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

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