My Cloud: Improper Restriction of Operations within the Bounds of a Memory Buffer
CVE-2024-22170 is a critical-severity improper restriction of operations within the bounds of a memory buffer vulnerability in My Cloud from Western Digital, with a CVSS 4.0 base score of 9.2 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 5.29.102 as the first without the flaw, so updating My Cloud to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.47% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update My Cloud to 5.29.102 or a later version.
- Update wd_cloud_firmware to 5.29.102 or a later version.
- Update my_cloud_dl4100_firmware to 5.29.102 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Western Digital | My Cloud | before 5.29.102 | 5.29.102 |
| Westerndigital | wd_cloud_firmware | before 5.29.102 | 5.29.102 |
| Westerndigital | my_cloud_dl4100_firmware | before 5.29.102 | 5.29.102 |
| Westerndigital | my_cloud_dl2100_firmware | before 5.29.102 | 5.29.102 |
| Westerndigital | my_cloud_ex2100_firmware | before 5.29.102 | 5.29.102 |
| Westerndigital | my_cloud_mirror_g2_firmware | before 5.29.102 | 5.29.102 |
| Westerndigital | my_cloud_firmware | before 5.29.102 | 5.29.102 |
| Westerndigital | my_cloud_pr4100_firmware | before 5.29.102 | 5.29.102 |
| Westerndigital | my_cloud_pr2100_firmware | before 5.29.102 | 5.29.102 |
| Westerndigital | my_cloud_ex4100_firmware | before 5.29.102 | 5.29.102 |
| Westerndigital | my_cloud_ex2_ultra_firmware | before 5.29.102 | 5.29.102 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Attack requirements
- PresentThe target must be in a specific state or configuration for the attack to work.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Confidentiality (vulnerable system)
- HighSerious loss of confidentiality on the vulnerable system.
- Integrity (vulnerable system)
- HighSerious loss of integrity on the vulnerable system.
- Availability (vulnerable system)
- HighSerious loss of availability on the vulnerable system.
- Confidentiality (other systems)
- NoneNo loss of confidentiality on systems beyond the vulnerable one.
- Integrity (other systems)
- NoneNo loss of integrity on systems beyond the vulnerable one.
- Availability (other systems)
- NoneNo loss of availability on systems beyond the vulnerable one.
Vector: 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. Scored by CNA (wdc.com).
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Restriction of Operations within the Bounds of a Memory Buffer
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary.
How developers prevent this class of flaw
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in My Cloud
- 9.3 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 7.8 High severity
- 9.8 Critical severity
- 9.8 Critical severity
Recent Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.8 High severity
- 7.8 High severity
- 8.8 High severity
- 8.8 High severity
Spotted an error? Tell us.