# CVE-2023-22819: Uncontrolled resource consumption vulnerability in Western Digital My Cloud, My Cloud Home and SanDisk ibi products

> An attacker with root privileges can cause a denial of service by consuming excessive memory in Western Digital NAS devices.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Feb 2024
- **Updated:** 5 Sep 2024
- **Also known as:** GHSA-4m5c-7v8f-8p2q

## What is CVE-2023-22819?

CVE-2023-22819 is a medium-severity denial of service vulnerability in SanDisk My Cloud Home & Duo, published on 5 Feb 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An uncontrolled resource consumption vulnerability issue that could arise by sending crafted requests to a service to consume a large amount of memory, eventually resulting in the service being stopped and restarted 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 the attacker to already have root privileges in order to exploit this vulnerability. This issue affects My Cloud Home and My Cloud Home Duo: before 9.5.1-104; ibi: before 9.5.1-104; My Cloud OS 5: before 5.27.161.

Weakness: CWE-400 (Uncontrolled Resource Consumption), CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2023-22819?

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 Glacier Firmware, Westerndigital My Cloud Home Duo Firmware, Westerndigital My Cloud Home Firmware, Westerndigital My Cloud Mirror G2 Firmware, Westerndigital My Cloud Pr4100 Firmware, Westerndigital Sandisk Ibi Firmware, Westerndigital Wd Cloud Firmware.

## How do I fix CVE-2023-22819?

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

## Is CVE-2023-22819 being exploited?

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

## Other vulnerabilities in SanDisk My Cloud Home & Duo

- [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-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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-22819 and fix it if it is affected.

What it is: CVE-2023-22819 is a medium-severity denial of service vulnerability in SanDisk My Cloud Home & Duo, published on 5 Feb 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-22819 in the wild and no public exploit code.

Affected product: SanDisk 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-2023-22819/ (Markdown: https://insights.sbomify.com/CVE-2023-22819/index.md)
```

## Sources

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

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