# CVE-2022-22995: Western Digital My Cloud OS 5 and My Cloud Home Unauthenticated Arbitrary File Write Vulnerability in Netatalk

> Unauthenticated attackers can write arbitrary files via SMB/AFP primitives to execute code on Western Digital My Cloud devices.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Mar 2022
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2022-22995, DLA-3706-1, GHSA-wc8x-f5rv-3653, MGASA-2024-0201, SUSE-SU-2023:4084-1, UBUNTU-CVE-2022-22995, USN-6786-1

## What is CVE-2022-22995?

CVE-2022-22995 is a critical path traversal vulnerability in Fedoraproject Fedora, published on 25 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The combination of primitives offered by SMB and AFP in their default configuration allows the arbitrary writing of files. By exploiting these combination of primitives, an attacker can execute arbitrary code.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

It affects 13 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `netatalk` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 3.1.0-3.22.1 |
| `netatalk` | SUSE:Linux Enterprise Workstation Extension 12 SP5 | All versions | 3.1.0-3.22.1 |

Products: Fedoraproject Fedora, Netatalk Netatalk, 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 Firmware, Westerndigital My Cloud Mirror Gen 2 Firmware, Westerndigital My Cloud Pr2100 Firmware, Westerndigital My Cloud Pr4100 Firmware, Westerndigital Wd Cloud Firmware.

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

Apply the vendor's patch.

## Is CVE-2022-22995 being exploited?

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

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-22995 is a critical path traversal vulnerability in Fedoraproject Fedora, published on 25 Mar 2022. 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-22995 in the wild and no public exploit code.

Affected product: Fedoraproject Fedora. 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-22995/ (Markdown: https://insights.sbomify.com/CVE-2022-22995/index.md)
```

## Sources

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

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