CVE-2022-36327
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 · uneditedImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability that could allow an attacker to write files to locations with certain critical filesystem types leading to remote code execution was discovered in Western Digital My Cloud Home, My Cloud Home Duo, SanDisk ibi and Western Digital My Cloud OS 5 devices. This issue requires an authentication bypass issue to be triggered before this can be exploited. This issue affects My Cloud Home and My Cloud Home Duo: before 9.4.0-191; ibi: before 9.4.0-191; My Cloud OS 5: before 5.26.202.
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 vulnerability in Western Digital My Cloud Home, My Cloud Home Duo, SanDisk ibi, and My Cloud OS 5 devices allows authenticated attackers to write files to restricted filesystem locations, leading to remote code execution. This issue requires an authentication bypass to be chained with the path traversal for exploitation.
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.202< 9.4.0-191< 9.4.0-191< 9.4.0-191CVSS 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 the device modelAccess the device dashboard or check the product label to confirm the exact model: Western Digital My Cloud OS 5, My Cloud Home, My Cloud Home Duo, or SanDisk ibi.Affected if The device is any of these four models.
-
Check the firmware versionIn the device web interface, navigate to Settings > About or Settings > Firmware to view the installed version. Alternatively, access the device via SSH or API and run: cat /etc/os-release or look for a version file in /etc.Affected if For My Cloud OS 5: version is below 5.26.202. For My Cloud Home, My Cloud Home Duo, or SanDisk ibi: version is below 9.4.0-191.
-
Verify the device web interface is accessibleAttempt to reach the device web interface via HTTP/HTTPS on the local network using the device IP address.Affected if The web interface is accessible and responds to requests.
-
Confirm authentication is required for the vulnerable endpointTest the API endpoints that handle file operations by sending a request without valid credentials. Observe whether the endpoint returns an authentication error or accepts the request.Affected if The endpoint accepts requests without valid authentication, indicating an authentication bypass exists that could be chained with this path traversal.
-
Inspect for unexpected files in restricted directoriesIf you have administrative access, review the filesystem for newly created or unexpected files in directories such as /www, /var/www, or the web root. Use: find /var/www -type f -mtime -30 or similar to locate recently modified files.Affected if Unexpected scripts, web shells, or executable files are found in restricted directories that should not contain user-uploaded content.
The device is affected if it is one of the four listed models and runs firmware version below the specified thresholds, with the web interface exposed and accessible.
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.2029.4.0-191
Update My Cloud Home, My Cloud Home Duo, and ibi to firmware version 9.4.0-191 or later, and My Cloud OS 5 to version 5.26.202 or later to remediate this vulnerability.
My Cloud OS 5: version 5.26.202 or later; My Cloud Home/Home Duo/Sandisk ibi: version 9.4.0-191 or later
- 1. Identify the specific Western Digital My Cloud device model (My Cloud OS 5, My Cloud Home, My Cloud Home Duo, or SanDisk ibi)
- 2. Access the device admin interface via web browser
- 3. Navigate to Settings or Administration section to check current firmware version
- 4. Download the firmware update from the official Western Digital support website for your specific device
- 5. In the admin interface, locate the firmware update or system update option
- 6. Upload and apply the downloaded firmware file
- 7. Allow the device to reboot and complete the update process
- 8. Verify the firmware has been updated to the fixed version (My Cloud OS 5: 5.26.202 or later; My Cloud Home/Home Duo/Sandisk ibi: 9.4.0-191 or later)
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-36327 — 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-36327 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