CVE-2022-29844
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 · uneditedA vulnerability in the FTP service of Western Digital My Cloud OS 5 devices running firmware versions prior to 5.26.119 allows an attacker to read and write arbitrary files. This could lead to a full NAS compromise and would give remote execution capabilities to the attacker.
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 confidenceA path traversal or similar vulnerability in the FTP service of Western Digital My Cloud OS 5 devices allows unauthenticated attackers to read and write arbitrary files on the NAS filesystem. This enables full device compromise and remote code execution.
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< 5.26.119< 5.26.119< 5.26.119< 5.26.119< 5.26.119< 5.26.119< 5.26.119< 5.26.119CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify your My Cloud device modelLocate the model name on the device label or check the My Cloud dashboard for the exact model number (such as Pr2100, Pr4100, Ex4100, Ex2 Ultra, Mirror G2, Dl2100, Dl4100, or Ex2100)Affected if The device is one of the eight models listed in the affected products
-
Check the installed firmware versionIn the My Cloud OS 5 web interface, navigate to Settings > About or Settings > General to view the current firmware versionAffected if The firmware version is less than 5.26.119
-
Confirm FTP service is enabledIn the My Cloud OS 5 dashboard, go to Settings > Network or Settings > Services and locate the FTP server setting to verify whether the service is turned onAffected if FTP is enabled and the firmware version is below 5.26.119
The environment is affected if the device runs My Cloud OS 5 firmware prior to version 5.26.119 and has the FTP service enabled.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.26.119
Upgrade Western Digital My Cloud OS 5 firmware to version 5.26.119 or later. If immediate patching is not possible, disable the FTP service as a compensating control.
My Cloud OS 5 firmware version 5.26.119 or later
- 1. Access the Western Digital My Cloud device web interface.
- 2. Navigate to Settings or Administration section.
- 3. Check the current firmware version under System or About section.
- 4. If firmware version is below 5.26.119, locate the firmware update option.
- 5. Download the latest firmware update (version 5.26.119 or later) from the official Western Digital support website.
- 6. Apply the firmware update through the web interface or according to WD's update procedure.
- 7. After the update completes, verify the new firmware version is 5.26.119 or higher.
- 8. Optionally, after patching, consider disabling the FTP service if not required, or ensuring FTP access is properly restricted.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29844 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-29844 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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