dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2024-22170

CRITICAL · 9.2 CVSS v4.0 Published 2024-09-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in Western Digital My Cloud ddns-start on Linux allows Overflow Buffers.This issue affects My Cloud: before 5.29.102.

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

Buffer overflow vulnerability in the ddns-start dynamic DNS service component of Western Digital My Cloud network-attached storage devices running Linux. The flaw allows overflow of memory buffers in the ddns-start binary, potentially enabling remote code execution. This affects all versions before firmware 5.29.102.

MitigationUpdate My Cloud firmware to version 5.29.102 or later to patch the vulnerability. If immediate patching is not possible, consider disabling the ddns-start service or isolating the device on a restricted network segment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Confirm device is Western Digital My Cloud
    Identify the device model through web UI, system settings, or command line (e.g., 'cat /proc/cpuinfo', 'nvram get model', or check the administrative interface)
    Affected if Device is not a Western Digital My Cloud NAS - the vulnerability only affects this product line
  2. Check firmware version
    Access the My Cloud dashboard via web UI (Settings > About) or use command line (e.g., 'cat /etc/version', 'nvram get firmware_version', or check the /etc/os-release file)
    Affected if Firmware version is present and less than 5.29.102 (for example, 5.26.100, 5.28.001, etc.)
  3. Verify ddns-start component exists
    Locate the ddns-start binary on the system using file system inspection commands (e.g., 'find / -name ddns-start 2>/dev/null' or check common binary directories like /usr/bin, /bin)
    Affected if The ddns-start binary is found on the device - this indicates the vulnerable component is installed
  4. Confirm Dynamic DNS service is enabled
    Check the My Cloud web interface for Dynamic DNS configuration (Settings > Network > Dynamic DNS) or inspect running processes for ddns-related services (e.g., 'ps aux | grep -i ddns')
    Affected if Dynamic DNS feature is configured or the ddns-start process is running/enabled

If the device is a Western Digital My Cloud NAS with firmware version below 5.29.102 and the ddns-start dynamic DNS component is present or enabled, the environment is affected by CVE-2024-22170.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update My Cloud firmware to version 5.29.102 or later to patch the vulnerability. If immediate patching is not possible, consider disabling the ddns-start service or isolating the device on a restricted network segment.

Recommended fix High confidence

5.29.102 or later

  1. 1. Identify your specific Western Digital My Cloud device model
  2. 2. Check the current firmware version of your My Cloud device through the web interface
  3. 3. Navigate to Western Digital's official support page at www.westerndigital.com
  4. 4. Locate and download firmware version 5.29.102 or later for your specific My Cloud model
  5. 5. Access the My Cloud admin interface and navigate to the firmware update section
  6. 6. Upload and apply the firmware update following the on-screen instructions
  7. 7. Verify the firmware has been successfully updated by checking the version in the admin interface

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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