dbcve.org
My Cloud OsOperating system · Westerndigital

CVE-2022-22992

CRITICAL · 9.8 CVSS v3.1 Published 2022-01-28
Fix available
A fix is available. Upgrade to 5.19.117 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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 command injection remote code execution vulnerability was discovered on Western Digital My Cloud Devices that could allow an attacker to execute arbitrary system commands on the device. The vulnerability was addressed by escaping individual arguments to shell functions coming from user input.

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 · moderate confidence

A command injection vulnerability in Western Digital My Cloud devices allows remote attackers to execute arbitrary system commands by injecting shell metacharacters into user input that is passed to shell functions without proper escaping. The vulnerability stems from the failure to sanitize user-supplied input before it is used in shell command execution.

MitigationApply the Western Digital firmware update that addresses this vulnerability. If updates are unavailable, network segmentation and restricting access to the device's management interface can reduce exposure until a patch is available.

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

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

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

  1. Identify the device as a Western Digital My Cloud product
    Access the device admin panel or check the device label/marketing to confirm it is a Western Digital My Cloud NAS device
    Affected if The device is not a Western Digital My Cloud product
  2. Determine the installed firmware version
    Log into the My Cloud dashboard, navigate to Settings > About or look for a firmware version displayed on the main status page. Alternatively, check the system information page or firmware update section
    Affected if The firmware version cannot be determined or is less than 5.19.117
  3. Verify the firmware version is vulnerable
    Compare the installed firmware version number against the affected range: versions prior to 5.19.117 are vulnerable
    Affected if The installed version is 5.19.116 or earlier
  4. Confirm management interface accessibility
    Determine if the My Cloud web management interface (typically on ports 80 or 443) is accessible from the network. Check router/firewall rules and device network settings
    Affected if The management interface is exposed to untrusted networks and the firmware version is below 5.19.117

The device is affected if it is a Western Digital My Cloud NAS running firmware version 5.19.116 or earlier with its management interface accessible.

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 the Western Digital firmware update that addresses this vulnerability. If updates are unavailable, network segmentation and restricting access to the device's management interface can reduce exposure until a patch is available.

Recommended fix Moderate confidence

My Cloud OS version 5.19.117 or later

  1. Log into the My Cloud OS web interface
  2. Navigate to Settings > Firmware Update or equivalent section
  3. Check current firmware version under About/Support
  4. If version is below 5.19.117, download the latest firmware update from the official Western Digital support site (www.westerndigital.com)
  5. Upload and apply the firmware update following the on-screen instructions
  6. Allow the device to complete the update process and reboot
  7. After reboot, verify the firmware has been updated to version 5.19.117 or later

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

Fix this in My Cloud Os Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22992 — 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-22992 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