dbcve.org
My Cloud Pr2100 FirmwareOperating system · Westerndigital

CVE-2022-29843

CRITICAL · 9.8 CVSS v3.1 Published 2023-01-26
Fix available
A fix is available. Upgrade to 5.26.119 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 vulnerability in the DDNS service configuration of Western Digital My Cloud OS 5 devices running firmware versions prior to 5.26.119 allows an attacker to execute code in the context of the root 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 confidence

A command injection vulnerability exists in the DDNS (Dynamic DNS) service configuration of Western Digital My Cloud OS 5 devices. User-supplied input in the DDNS configuration is not properly sanitized, allowing an attacker to inject and execute arbitrary shell commands with root privileges.

MitigationUpdate Western Digital My Cloud OS 5 firmware to version 5.26.119 or later. If patching is not immediately possible, restrict network access to the device's administrative interfaces and disable the DDNS service if not required.

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 Pr2100 FirmwareOperating system
Affected:< 5.26.119
My Cloud Pr4100 FirmwareOperating system
Affected:< 5.26.119
My Cloud Ex4100 FirmwareOperating system
Affected:< 5.26.119
My Cloud Ex2 Ultra FirmwareOperating system
Affected:< 5.26.119
My Cloud Mirror G2 FirmwareOperating system
Affected:< 5.26.119
My Cloud Dl2100 FirmwareOperating system
Affected:< 5.26.119
My Cloud Dl4100 FirmwareOperating system
Affected:< 5.26.119
My Cloud Ex2100 FirmwareOperating system
Affected:< 5.26.119

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 your My Cloud device model
    Locate the model name on the device label or check via the My Cloud web interface under Settings > System > About
    Affected if The model is one of: Pr2100, Pr4100, Ex4100, Ex2 Ultra, Mirror G2, Dl2100, Dl4100, Ex2100
  2. Check installed firmware version
    In the My Cloud web interface, navigate to Settings > System > About and locate the Firmware Version field. Alternatively, access the device via SSH and run: cat /etc/version
    Affected if The firmware version is lower than 5.26.119 (for example, 5.25.x or earlier)
  3. Verify DDNS service status
    In the My Cloud web interface, go to Settings > Network > DDNS and check whether Dynamic DNS is enabled. If DDNS is disabled, the attack surface is not exposed.
    Affected if DDNS is currently enabled and configured with a provider (such as DynDNS, No-IP, or others)
  4. Inspect DDNS configuration entries
    If you have SSH access, examine the DDNS configuration files in /etc/ddns/ or the system configuration database. Look for any custom DDNS provider entries or scripts that may contain user-supplied data.
    Affected if Non-default DDNS providers are configured or custom DDNS update scripts are present

Your device is affected if it is a listed My Cloud model running firmware below version 5.26.119 AND the DDNS service is enabled with a custom or non-default configuration.

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.26.119 or later
Fixed in 5.26.119
Interim mitigation

Update Western Digital My Cloud OS 5 firmware to version 5.26.119 or later. If patching is not immediately possible, restrict network access to the device's administrative interfaces and disable the DDNS service if not required.

Recommended fix High confidence

Firmware 5.26.119 or later for My Cloud OS 5 devices (Pr2100, Pr4100, Ex4100, Ex2 Ultra, Mirror G2, Dl2100, Dl4100, Ex2100)

  1. 1. Log in to the My Cloud OS 5 web interface as administrator
  2. 2. Navigate to Settings or Administration section
  3. 3. Locate the Firmware Update or System Update option
  4. 4. Check for available updates or manually download firmware version 5.26.119 or later from Western Digital's support website
  5. 5. Upload and install the firmware update
  6. 6. After installation, restart the device to complete the update process
  7. 7. Verify the firmware version has been updated to 5.26.119 or later
Caveat Firmware updates may temporarily disrupt device availability; ensure backups are performed before updating

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

Fix this in My Cloud Pr2100 Firmware 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-29843 — 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-29843 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