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

> Low-privilege users can execute arbitrary code as root on Western Digital My Cloud devices by exploiting symlink handling in file upload commands.

- **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 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qv94-w6rj-6f5p

## What is CVE-2019-9949?

CVE-2019-9949 is a high-severity path traversal vulnerability in n/a, published on 23 May 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Western Digital My Cloud Cloud, Mirror Gen2, EX2 Ultra, EX2100, EX4100, DL2100, DL4100, PR2100 and PR4100 before firmware 2.31.183 are affected by a code execution (as root, starting from a low-privilege user session) vulnerability. The cgi-bin/webfile_mgr.cgi file allows arbitrary file write by abusing symlinks. Specifically, this occurs by uploading a tar archive that contains a symbolic link, then uploading another archive that writes a file to the link using the "cgi_untar" command. Other commands might also be susceptible. Code can be executed because the "name" parameter passed to the cgi_unzip command is not sanitized.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

It affects 9 products.


Products: Westerndigital My Cloud Dl2100 Firmware, Westerndigital My Cloud Dl4100 Firmware, Westerndigital My Cloud Ex2100 Firmware, Westerndigital My Cloud Ex2 Ultra Firmware, Westerndigital My Cloud Ex4100 Firmware, Westerndigital My Cloud Firmware, Westerndigital My Cloud Mirror Gen2 Firmware, Westerndigital My Cloud Pr2100 Firmware, Westerndigital My Cloud Pr4100 Firmware.

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

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

## Is CVE-2019-9949 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-36331](https://insights.sbomify.com/CVE-2022-36331/): Impersonation attack causing an Authentication Bypass on Western Digital devices (critical 10.0)
- [CVE-2019-9950](https://insights.sbomify.com/CVE-2019-9950/): Auth bypass in n/a (critical 9.8)
- [CVE-2022-22999](https://insights.sbomify.com/CVE-2022-22999/): Cross-site Scripting Vulnerability in USB Backups App (high 8.2)
- [CVE-2022-23000](https://insights.sbomify.com/CVE-2022-23000/): Weak Default SSL use in Port Forwarding Service (high 7.3)
- [CVE-2022-29844](https://insights.sbomify.com/CVE-2022-29844/): Western Digital My Cloud OS 5 arbitrary file read and write vulnerability via ftp (medium 6.7)

## Fix prompt for AI coding agents

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

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

## Sources

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

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