CVE-2019-9950
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWestern 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAuthentication bypass in WD My Cloud devices where login_mgr.cgi validates credentials against /etc/shadow but the 'nobody' account uses a default empty password, allowing attackers to access the control panel API as a low-privilege user and modify web source code to escalate to non-Admin device access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.31.174< 2.31.174< 2.31.174< 2.31.174< 2.31.174< 2.31.174< 2.31.174< 2.31.174CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check the installed firmware versionAccess the device web interface and navigate to Settings > About, or use the command 'cat /etc/version' via SSH/Telnet if available. Compare the version number to 2.31.174.Affected if The firmware version is less than 2.31.174 (for example, 2.30.XXX or earlier).
-
Inspect the nobody account password in /etc/shadowIf you have shell access (SSH/Telnet), run 'grep nobody /etc/shadow' to examine the password hash field. Look for entries where the second field is empty or matches the pattern for no password.Affected if The nobody account has an empty password field (the second field is blank or starts with '$' but is unset), indicating no password is required.
-
Verify login_mgr.cgi endpoint accessibilityAttempt to access the login_mgr.cgi endpoint on the device's web interface (typically at http://[device-ip]/cgi-bin/login_mgr.cgi). Observe if authentication can be bypassed or if requests are processed without proper credential validation.Affected if The endpoint responds without requiring valid admin credentials or accepts the 'nobody' username with an empty password for API access.
Your device is affected if it runs firmware versions below 2.31.174 AND has the 'nobody' account configured with an empty password, allowing unauthenticated or low-privilege access via the login_mgr.cgi API.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.31.174
Update firmware to version 2.31.174 or later on all affected My Cloud devices; if immediate patching is impossible, disable the 'nobody' account or implement network segmentation to restrict admin interface access.
Firmware version 2.31.174 or later for your specific WD My Cloud device
- Identify your specific WD My Cloud device model from the affected list (My Cloud, My Cloud Mirror Gen2, My Cloud EX2 Ultra, My Cloud EX2100, My Cloud EX4100, My Cloud DL2100, My Cloud DL4100, or My Cloud PR2100)
- Navigate to the official Western Digital support site (support.wdc.com) and locate the firmware download page for your specific device model
- Download firmware version 2.31.174 or later for your device
- Access the My Cloud web interface using your current admin credentials
- Navigate to Settings > Firmware Update or Settings > Administration > Firmware Update
- Upload the downloaded firmware file and apply the update
- After the firmware update completes, verify the new firmware version is 2.31.174 or higher
- Confirm the vulnerability is no longer present by verifying the 'nobody' account no longer has an empty password or is properly secured
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9950 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-9950 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data