# CVE-2019-9950: Auth bypass in n/a

> Attackers can bypass authentication using the default empty password for the 'nobody' account to gain low-privilege access and modify web content on Western Digital My Cloud devices.

- **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:** 24 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rv3g-3684-4ppw

## What is CVE-2019-9950?

CVE-2019-9950 is a critical authentication bypass vulnerability in n/a, published on 24 Apr 2019. 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 Mirror Gen2, My Cloud EX2 Ultra, My Cloud EX2100, My Cloud EX4100, My Cloud DL2100, My Cloud DL4100, My Cloud PR2100 and My Cloud PR4100 firmware before 2.31.174 is affected by an authentication bypass vulnerability. The login_mgr.cgi file checks credentials against /etc/shadow. However, the "nobody" account (which can be used to access the control panel API as a low-privilege logged-in user) has a default empty password, allowing an attacker to modify the My Cloud EX2 Ultra web page source code and obtain access to the My Cloud as a non-Admin My Cloud device user.

Weakness: CWE-521 (Weak Password Requirements)

## Which versions are affected by CVE-2019-9950?

It affects 9 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 Mirror Gen2 Firmware, Westerndigital My Cloud Pr2100 Firmware, Westerndigital My Cloud Pr4100 Firmware.

## How do I fix CVE-2019-9950?

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

## Is CVE-2019-9950 being exploited?

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

## Other vulnerabilities in n/a

- [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-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-2019-9950 and fix it if it is affected.

What it is: CVE-2019-9950 is a critical authentication bypass vulnerability in n/a, published on 24 Apr 2019. 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-2019-9950 in the wild and no public exploit code.

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

## Sources

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

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