dbcve.org
My Cloud Home FirmwareOperating system · Westerndigital

CVE-2022-36329

HIGH · 7.5 CVSS v3.1 Published 2023-05-10
Fix available
A fix is available. Upgrade to 9.4.0-191 or later.
See remediation →
84/100
Remediation priority · High
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
An improper privilege management issue that could allow an attacker to cause a denial of service over the OTA mechanism was discovered in Western Digital My Cloud Home, My Cloud Home Duo and SanDisk ibi devices.This issue affects My Cloud Home and My Cloud Home Duo: before 9.4.0-191; ibi: before 9.4.0-191.

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

This is an improper privilege management vulnerability in the OTA (Over-The-Air) update mechanism of Western Digital My Cloud Home, My Cloud Home Duo, and SanDisk ibi devices. The flaw allows an attacker to cause denial of service by exploiting insufficient access controls in the OTA update process, likely through manipulating update requests or authenticated sessions.

MitigationUpgrade affected devices to firmware version 9.4.0-191 or later to remediate this vulnerability. Organizations should prioritize patching devices exposed to untrusted networks given the OTA attack vector.

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 Home FirmwareOperating system
Affected:< 9.4.0-191
My Cloud Home Duo FirmwareOperating system
Affected:< 9.4.0-191
Sandisk Ibi FirmwareOperating system
Affected:< 9.4.0-191

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 model
    Locate the physical device or log into the device admin interface and identify the exact model name (My Cloud Home, My Cloud Home Duo, or SanDisk ibi).
    Affected if The device is not one of these three models, the check does not apply.
  2. Check the installed firmware version
    Access the device dashboard or settings panel, typically found under Settings > About or System > Firmware, and note the firmware version number displayed.
    Affected if The firmware version is lower than 9.4.0-191, indicating the device is running a vulnerable version.
  3. Verify firmware version via CLI if available
    If SSH or command-line access is enabled, log in and run the appropriate version check command (such as `cat /etc/version` or `version` depending on the device's shell).
    Affected if The reported version string is below 9.4.0-191, confirming the vulnerability is present.
  4. Confirm OTA update mechanism is enabled
    Access the device settings and check the OTA/Update configuration section to determine if automatic updates are enabled or if the update service is accessible.
    Affected if The OTA update feature is enabled or accessible, making the device potentially exploitable over the network.

The device is affected if it is a My Cloud Home, My Cloud Home Duo, or SanDisk ibi running firmware version lower than 9.4.0-191 with the OTA update feature 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 9.4.0-191 or later
Fixed in 9.4.0-191
Interim mitigation

Upgrade affected devices to firmware version 9.4.0-191 or later to remediate this vulnerability. Organizations should prioritize patching devices exposed to untrusted networks given the OTA attack vector.

Recommended fix High confidence

My Cloud Home Firmware: 9.4.0-191 | My Cloud Home Duo Firmware: 9.4.0-191 | Sandisk Ibi Firmware: 9.4.0-191

  1. Access the device's web-based administration interface
  2. Navigate to the Settings or System section
  3. Locate the Firmware Update option
  4. Check for available updates or manually download firmware version 9.4.0-191 from Western Digital's official support website
  5. Follow the on-screen instructions to apply the firmware update
  6. Verify the update was successful by checking the firmware version after rebooting

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

Fix this in My Cloud Home Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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