dbcve.org
My Cloud Pr2100 FirmwareOperating system · Westerndigital

CVE-2023-22817

MEDIUM · 5.5 CVSS v3.1 Published 2024-02-05
Fix available
A fix is available. Upgrade to 5.27.161 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Server-side request forgery (SSRF) vulnerability that could allow a rogue server on the local network to modify its URL using another DNS address to point back to the loopback adapter. This could then allow the URL to exploit other vulnerabilities on the local server. This was addressed by fixing DNS addresses that refer to loopback. This issue affects My Cloud OS 5 devices before 5.27.161, My Cloud Home, My Cloud Home Duo and SanDisk ibi devices before 9.5.1-104. 

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

Server-side request forgery (SSRF) vulnerability in WD My Cloud devices allows a rogue server on the local network to manipulate DNS resolution to point back to the loopback adapter, enabling exploitation of other local vulnerabilities. The fix involves proper validation and filtering of DNS addresses that resolve to the loopback interface (127.0.0.0/8).

MitigationUpdate My Cloud OS 5 devices to firmware version 5.27.161 or later, and My Cloud Home/Home Duo/SanDisk ibi devices to version 9.5.1-104 or later to address the improper DNS loopback address validation.

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

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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 WD My Cloud device model
    Log into the My Cloud web interface and locate the device model name, typically found in the dashboard or under Settings > Device > Overview
    Affected if The device model is one of: Pr2100, Pr4100, Ex4100, Ex2 Ultra, Mirror G2, Dl2100, Dl4100, or Ex2100
  2. Locate the firmware version in the device interface
    In the My Cloud web UI, navigate to Settings > About or Settings > Device > Firmware Version to find the currently installed firmware version
    Affected if A firmware version is displayed and is below 5.27.161
  3. Compare the installed version against the affected range
    Compare the firmware version number found in the About section to 5.27.161 using standard version comparison (for example, 5.27.100 is lower than 5.27.161)
    Affected if The installed firmware version is less than 5.27.161 (for example, 5.26.200, 5.27.100, or any version starting with 5.26.x or earlier)
  4. Confirm the My Cloud OS 5 is in use
    Verify the device is running My Cloud OS 5 firmware (not the older My Cloud OS 3) by checking the firmware version format or the web UI branding
    Affected if The device runs My Cloud OS 5 with firmware version < 5.27.161

You are affected if you own a WD My Cloud device (Pr2100, Pr4100, Ex4100, Ex2 Ultra, Mirror G2, Dl2100, Dl4100, or Ex2100) running firmware version 5.27.160 or lower.

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.27.161 or later
Fixed in 5.27.161
Interim mitigation

Update My Cloud OS 5 devices to firmware version 5.27.161 or later, and My Cloud Home/Home Duo/SanDisk ibi devices to version 9.5.1-104 or later to address the improper DNS loopback address validation.

Recommended fix High confidence

5.27.161

  1. 1. Access the My Cloud device admin interface via web browser
  2. 2. Navigate to Settings > Firmware Update or Maintenance > Firmware Update
  3. 3. Check the current firmware version to confirm it is below 5.27.161
  4. 4. Download firmware version 5.27.161 from the official Western Digital support website (www.westerndigital.com)
  5. 5. In the admin interface, select the option to upload and install the firmware file
  6. 6. Wait for the firmware update process to complete - do not power off the device during this process
  7. 7. After the device reboots, verify the firmware has been updated to 5.27.161 or later

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

Fix this in My Cloud Pr2100 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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