dbcve.org
My Cloud OsOperating system · Westerndigital

CVE-2022-22990

HIGH · 8.8 CVSS v3.1 Published 2022-01-13
Fix available
A fix is available. Upgrade to 5.19.117 or later.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click

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 · unedited
A limited authentication bypass vulnerability was discovered that could allow an attacker to achieve remote code execution and escalate privileges on the My Cloud devices. Addressed this vulnerability by changing access token validation logic and rewriting rule logic on PHP scripts.

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 confidence

This is an authentication bypass vulnerability in Western Digital My Cloud network-attached storage (NAS) devices. The flaw allows attackers to circumvent limited authentication controls and achieve remote code execution with elevated privileges. The vulnerability stems from inadequate access token validation and flawed rule logic in PHP scripts.

MitigationApply vendor-supplied firmware updates immediately. If patches are unavailable, restrict network access to My Cloud devices and monitor for unauthorized access attempts.

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
My Cloud OsOperating system
Affected:< 5.19.117

CVSS 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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the device is a Western Digital My Cloud NAS
    Access the device web interface (typically at mycloud.com or the device's IP address) and check the device model/name in the settings or dashboard. Alternatively, check for WD My Cloud-specific services on the network.
    Affected if The device is NOT a Western Digital My Cloud NAS - the CVE does not apply to other vendors' products.
  2. Determine the installed My Cloud OS firmware version
    Log into the My Cloud web interface, navigate to Settings > About or Settings > System, and locate the firmware version displayed. Compare this version number to 5.19.117.
    Affected if The installed firmware version is below 5.19.117 - this indicates the device is running a vulnerable version.
  3. Check if remote access or cloud access is enabled
    In the My Cloud web interface, go to Settings > Cloud Access or Settings > Remote Access and verify whether remote/cloud connectivity is enabled. The vulnerability allows bypassing authentication for remote access.
    Affected if Remote or cloud access is enabled, making the device directly reachable from external networks and increasing exposure to the authentication bypass.
  4. Review access logs for suspicious authentication patterns
    Check My Cloud system logs (Settings > Diagnostics > Log Files or similar) for failed authentication attempts, unusual IP addresses, or patterns of repeated login requests that may indicate exploitation attempts.
    Affected if Logs show authentication anomalies, unexpected IP addresses accessing the device, or evidence of unauthorized access attempts.

The device is affected if it is a Western Digital My Cloud NAS running firmware version below 5.19.117 with remote access enabled, exposing it to the authentication bypass vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 5.19.117 or later
Fixed in 5.19.117
Interim mitigation

Apply vendor-supplied firmware updates immediately. If patches are unavailable, restrict network access to My Cloud devices and monitor for unauthorized access attempts.

Recommended fix High confidence

My Cloud OS firmware version 5.19.117 or later

  1. Access the WD My Cloud web interface or mobile app
  2. Navigate to Settings > Firmware Update or similar firmware management section
  3. Check current firmware version (should be below 5.19.117)
  4. Update to the latest available firmware version (5.19.117 or later)
  5. Verify the update was successful by checking the firmware version after reboot

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in My Cloud Os Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22990 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-22990 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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