dbcve.org
My Cloud OsOperating system · Westerndigital

CVE-2022-22993

HIGH · 8.8 CVSS v3.1 Published 2022-01-28
Fix available
A fix is available. Upgrade to 5.19.117 or later.
See remediation →
93/100
Remediation priority · Urgent
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
A limited SSRF vulnerability was discovered on Western Digital My Cloud devices that could allow an attacker to impersonate a server and reach any page on the server by bypassing access controls. The vulnerability was addressed by creating a whitelist for valid parameters.

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

A limited Server-Side Request Forgery (SSRF) vulnerability in Western Digital My Cloud devices allows attackers to bypass access controls and reach arbitrary pages on the server by impersonating the server. The vulnerability was remediated by implementing a whitelist validation mechanism for request parameters.

MitigationApply the vendor patch from Western Digital that implements parameter whitelisting, or if no patch is available, manually restrict request parameters to a predefined set of allowed values to prevent unauthorized server-side requests.

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 OsOperating system
Affected:< 5.19.117

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

CVSS:3.1/AV:A/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm you are running a Western Digital My Cloud device
    Access the device's web administration interface (typically at mycloud.com or the device's local IP address) and check the dashboard or system settings for the device model name.
    Affected if The device model is not a Western Digital My Cloud product.
  2. Identify the installed My Cloud OS version
    In the web admin interface, navigate to Settings > About or Settings > System, and locate the firmware or OS version number displayed.
    Affected if Unable to locate the OS version in the admin interface.
  3. Compare your version against the affected range
    Take the version number found (for example, 5.19.105 or 5.18.200) and compare it numerically to 5.19.117. Any version lower than 5.19.117 is within the affected range.
    Affected if The installed version is less than 5.19.117 (for example, 5.19.116, 5.19.100, 5.18.x, or earlier).
  4. Check for the presence of the whitelist validation (optional verification)
    If you have CLI access, examine the web application configuration files for parameter validation logic. Look for any whitelist patterns that validate request parameters against a predefined allowed list.
    Affected if No whitelist validation is implemented in the application configuration.

You are affected if your Western Digital My Cloud device runs My Cloud OS version 5.19.117 or any earlier version.

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.19.117 or later
Fixed in 5.19.117
Interim mitigation

Apply the vendor patch from Western Digital that implements parameter whitelisting, or if no patch is available, manually restrict request parameters to a predefined set of allowed values to prevent unauthorized server-side requests.

Recommended fix Moderate confidence

My Cloud OS version 5.19.117 or later

  1. Log in to the Western Digital My Cloud dashboard as an administrator
  2. Navigate to Settings or System settings
  3. Look for a firmware update or system update option
  4. Check for available updates - the system should show version 5.19.117 or later
  5. If an update is available, click to download and install the firmware
  6. Wait for the update process to complete - do not power off the device during this process
  7. After the device restarts, verify the firmware version is 5.19.117 or later in the system settings
Caveat Review release notes for any new features or changes to functionality that may affect your configuration

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

Fix this in My Cloud Os Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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