# CVE-2022-36331: Impersonation attack causing an Authentication Bypass on Western Digital devices

> Unauthenticated attackers can impersonate users to bypass authentication and access private data on Western Digital My Cloud and SanDisk ibi devices.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 Jun 2023
- **Updated:** 3 Jan 2025
- **Also known as:** GHSA-q3w5-whrj-66qg

## What is CVE-2022-36331?

CVE-2022-36331 is a critical authentication bypass vulnerability in SanDisk My Cloud Home and My Cloud Home Duo, published on 12 Jun 2023. 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 Home, My Cloud Home Duo, and SanDisk ibi devices were vulnerable to an impersonation attack that could allow an unauthenticated attacker to gain access to user data.
This issue affects My Cloud OS 5 devices: before 5.25.132; My Cloud Home and My Cloud Home Duo: before 8.13.1-102; SanDisk ibi: before 8.13.1-102.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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

It affects 12 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 Home Duo Firmware, Westerndigital My Cloud Home Firmware, Westerndigital My Cloud Mirror G2 Firmware, Westerndigital My Cloud Pr2100 Firmware, Westerndigital My Cloud Pr4100 Firmware, Westerndigital Sandisk Ibi Firmware.

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

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

## Is CVE-2022-36331 being exploited?

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

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

- [CVE-2019-9950](https://insights.sbomify.com/CVE-2019-9950/): Auth bypass in n/a (critical 9.8)
- [CVE-2019-9949](https://insights.sbomify.com/CVE-2019-9949/): Path traversal in n/a (high 8.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-2022-36331 and fix it if it is affected.

What it is: CVE-2022-36331 is a critical authentication bypass vulnerability in SanDisk My Cloud Home and My Cloud Home Duo, published on 12 Jun 2023. 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-2022-36331 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-36331/ (Markdown: https://insights.sbomify.com/CVE-2022-36331/index.md)
```

## Sources

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

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