# CVE-2022-36327: Path traversal vulnerability leading to an arbitrary file write in Western Digital devices

> Path traversal allows arbitrary file writes leading to remote code execution on Western Digital NAS devices, requiring prior authentication bypass.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 May 2023
- **Updated:** 22 Jan 2025
- **Also known as:** GHSA-w8xh-67qr-h5gr

## What is CVE-2022-36327?

CVE-2022-36327 is a medium-severity path traversal vulnerability in SanDisk My Cloud Home and My Cloud Home Duo, published on 18 May 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability that could allow an attacker to write files to locations with certain critical filesystem types leading to remote code execution was discovered in Western Digital My Cloud Home, My Cloud Home Duo, SanDisk ibi and Western Digital My Cloud OS 5 devices. This issue requires an authentication bypass issue to be triggered before this can be exploited. 
This issue affects My Cloud Home and My Cloud Home Duo: before 9.4.0-191; ibi: before 9.4.0-191; My Cloud OS 5: before 5.26.202.

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

## Which versions are affected by CVE-2022-36327?

It affects 4 products.


Products: Westerndigital My Cloud Home Duo Firmware, Westerndigital My Cloud Home Firmware, Westerndigital My Cloud Os 5, Westerndigital Sandisk Ibi Firmware.

## How do I fix CVE-2022-36327?

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

## Is CVE-2022-36327 being exploited?

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

## Other vulnerabilities in SanDisk My Cloud Home and My Cloud Home Duo

- [CVE-2022-22998](https://insights.sbomify.com/CVE-2022-22998/): Protecting AWS credentials stored in plaintext on My Cloud Home (high 8.0)
- [CVE-2022-22997](https://insights.sbomify.com/CVE-2022-22997/): Command Injection Vulnerability on My Cloud Home (medium 6.8)
- [CVE-2022-36328](https://insights.sbomify.com/CVE-2022-36328/): Path Traversal Vulnerability leading to an arbitrary file read in Western Digital devices (medium 5.8)
- [CVE-2022-29837](https://insights.sbomify.com/CVE-2022-29837/): Path traversal Vulnerability in Western Digital My Cloud Home, My Cloud Home Duo and SanDisk ibi Devices (medium 4.7)
- [CVE-2022-36326](https://insights.sbomify.com/CVE-2022-36326/): Resource Exhaustion Vulnerability in Western Digital devices (medium 4.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-36327 and fix it if it is affected.

What it is: CVE-2022-36327 is a medium-severity path traversal vulnerability in SanDisk My Cloud Home and My Cloud Home Duo, published on 18 May 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-36327 in the wild and no public exploit code.

Affected product: SanDisk My Cloud Home and My Cloud Home Duo. 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-2022-36327/ (Markdown: https://insights.sbomify.com/CVE-2022-36327/index.md)
```

## Sources

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

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