# CVE-2017-17560: File upload in n/a

> Unauthenticated file upload in the web administration component allows attackers to upload a PHP shell and execute arbitrary code as root.

- **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:** 12 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gchv-qvcf-v9x3

## What is CVE-2017-17560?

CVE-2017-17560 is a critical vulnerability in n/a, published on 12 Dec 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 Western Digital MyCloud PR4100 2.30.172 devices. The web administration component, /web/jquery/uploader/multi_uploadify.php, provides multipart upload functionality that is accessible without authentication and can be used to place a file anywhere on the device's file system. This allows an attacker the ability to upload a PHP shell onto the device and obtain arbitrary code execution as root.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Westerndigital My Cloud Pr4100 Firmware.

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

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

## Is CVE-2017-17560 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-17560 exists.

Public exploit code:

- Western Digital MyCloud multi_uploadify File Upload Vulnerability (metasploit)
- Western Digital MyCloud - 'multi_uploadify' File Upload (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17560 is a critical vulnerability in n/a, published on 12 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-17560 exists.

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-17560/ (Markdown: https://insights.sbomify.com/CVE-2017-17560/index.md)
```

## Sources

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

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