# CVE-2019-9951: File upload in n/a

> Unauthenticated attackers can upload arbitrary files to any location on Western Digital My Cloud NAS devices, potentially leading to remote code execution.

- **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:** 24 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-f473-rqfr-w67p

## What is CVE-2019-9951?

CVE-2019-9951 is a critical vulnerability in n/a, published on 24 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Western Digital My Cloud, My Cloud Mirror Gen2, My Cloud EX2 Ultra, My Cloud EX2100, My Cloud EX4100, My Cloud DL2100, My Cloud DL4100, My Cloud PR2100 and My Cloud PR4100 firmware before 2.31.174 is affected by an unauthenticated file upload vulnerability. The page web/jquery/uploader/uploadify.php can be accessed without any credentials, and allows uploading arbitrary files to any location on the attached storage.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 9 products.


Products: Western Digital My Cloud Dl2100, Western Digital My Cloud Dl4100 Firmware, Western Digital My Cloud Ex2100 Firmware, Western Digital My Cloud Ex2 Ultra Firmware, Western Digital My Cloud Ex4100, Western Digital My Cloud Firmware, Western Digital My Cloud Mirror Gen 2 Firmware, Western Digital My Cloud Pr2100 Firmware, Western Digital My Cloud Pr4100.

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

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

## Is CVE-2019-9951 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-17153](https://insights.sbomify.com/CVE-2018-17153/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-9951 is a critical vulnerability in n/a, published on 24 Apr 2019. 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-2019-9951 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-9951/ (Markdown: https://insights.sbomify.com/CVE-2019-9951/index.md)
```

## Sources

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

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