# CVE-2019-8389: Path traversal in n/a

> An attacker on the same Wi-Fi network can read arbitrary files from the device via path traversal in the Musicloud app's transfer service.

- **Severity:** High 8.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Feb 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-x4j6-3g7m-37pr

## What is CVE-2019-8389?

CVE-2019-8389 is a high-severity path traversal vulnerability in n/a, published on 17 Feb 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A file-read vulnerability was identified in the Wi-Fi transfer feature of Musicloud 1.6. By default, the application runs a transfer service on port 8080, accessible by everyone on the same Wi-Fi network. An attacker can send the POST parameters downfiles and cur-folder (with a crafted ../ payload) to the download.script endpoint. This will create a MusicPlayerArchive.zip archive that is publicly accessible and includes the content of any requested file (such as the /etc/passwd file).

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

## Which versions are affected by CVE-2019-8389?

It affects 1 product.


Products: Musicloud Project Musicloud.

## How do I fix CVE-2019-8389?

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

## Is CVE-2019-8389 being exploited?

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

Public exploit code:

-  [CVE-2019-8389] An exploit code for exploiting a local file read vulnerability in Musicloud v1.6 iOS Application  (github_poc): https://github.com/shawarkhanethicalhacker/CVE-2019-8389

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-8389 and fix it if it is affected.

What it is: CVE-2019-8389 is a high-severity path traversal vulnerability in n/a, published on 17 Feb 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-8389 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-2019-8389/ (Markdown: https://insights.sbomify.com/CVE-2019-8389/index.md)
```

## Sources

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

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