dbcve.org
My Cloud OsOperating system · Westerndigital

CVE-2022-22991

HIGH · 8.8 CVSS v3.1 Published 2022-01-13
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 malicious user on the same LAN could use DNS spoofing followed by a command injection attack to trick a NAS device into loading through an unsecured HTTP call. Addressed this vulnerability by disabling checks for internet connectivity using HTTP.

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

This vulnerability in a NAS device allowed an attacker on the same local network to perform DNS spoofing to intercept HTTP-based internet connectivity checks, then inject malicious commands through this channel. The attack vector relied on the device using unsecured HTTP for connectivity verification, enabling both man-in-the-middle and command injection.

MitigationDisable or remove HTTP-based internet connectivity checks in the NAS firmware/configuration, replacing them with HTTPS or alternative secure methods to prevent DNS spoofing and command injection attacks.

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. Identify the device and firmware version
    Access the My Cloud dashboard via web browser (usually at mycloud.com or IP address), navigate to Settings > About, and record the firmware version displayed. Alternatively, check via SSH using 'cat /etc/version' if SSH is enabled.
    Affected if The firmware version is lower than 5.19.117, indicating the device is running a vulnerable version of My Cloud OS.
  2. Verify HTTP connectivity check configuration
    In the My Cloud web interface, navigate to Settings > Network > Connectivity or Settings > Network > Internet Access. Look for options related to internet connectivity verification or network status checks that may use HTTP (instead of HTTPS).
    Affected if HTTP-based internet connectivity checks or 'verify internet connection' features are enabled and configured to use unsecured HTTP.
  3. Check for exposed network services
    From a computer on the same network, use a browser or network scanner to check if the My Cloud device responds on HTTP (port 80) for its web interface and connectivity check endpoints.
    Affected if The device exposes HTTP services on the local network without HTTPS enforcement for connectivity verification features.
  4. Review network configuration for DNS settings
    In the My Cloud web interface under Settings > Network > TCP/IP, examine the DNS server configuration. Check if the device uses local or ISP-provided DNS that could be spoofed by an attacker on the same network.
    Affected if The device is configured to use easily-spoofable DNS servers on the local network, making DNS hijacking feasible.

A user is affected if they are running Western Digital My Cloud OS firmware versions prior to 5.19.117 with HTTP-based internet connectivity checks enabled on their local network.

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

Disable or remove HTTP-based internet connectivity checks in the NAS firmware/configuration, replacing them with HTTPS or alternative secure methods to prevent DNS spoofing and command injection attacks.

Recommended fix High confidence

My Cloud OS version 5.19.117 or later

  1. 1. Back up all critical data on the NAS before proceeding with firmware updates
  2. 2. Navigate to the official Western Digital support website (support.wdc.com) and locate the firmware download section for My Cloud OS
  3. 3. Download the firmware version 5.19.117 or later for your specific My Cloud device model
  4. 4. Log in to the My Cloud OS web interface as an administrator
  5. 5. Go to Settings > Administration or Settings > Firmware Update
  6. 6. Select the option to manually update firmware and upload the downloaded .bin file
  7. 7. Wait for the upload to complete - do not power off the device during this process
  8. 8. The device will automatically reboot after applying the update

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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 locally
dbcve dependency scanner

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