Skip to content
Fencer Intel
critical 9.8

CVE-2019-9950 json

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…

published 7y ago modified 4mo ago also EUVD-2019-19304

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.3%
EPSS 2.3% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

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.

Patch / fix

  • westerndigital my_cloud_firmware 2.31.174
  • westerndigital my_cloud_mirror_gen2_firmware 2.31.174
  • westerndigital my_cloud_ex2_ultra_firmware 2.31.174
  • westerndigital my_cloud_ex2100_firmware 2.31.174
  • westerndigital my_cloud_ex4100_firmware 2.31.174
  • westerndigital my_cloud_dl2100_firmware 2.31.174
  • westerndigital my_cloud_dl4100_firmware 2.31.174
  • westerndigital my_cloud_pr2100_firmware 2.31.174
  • westerndigital my_cloud_pr4100_firmware 2.31.174

Is CVE-2019-9950 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

2.30% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-521 Weak Password Requirements

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.