CVE-2022-22994
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 remote code execution vulnerability was discovered on Western Digital My Cloud devices where an attacker could trick a NAS device into loading through an unsecured HTTP call. This was a result insufficient verification of calls to the device. The vulnerability was addressed 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 confidenceA remote code execution vulnerability in Western Digital My Cloud NAS devices where insufficient verification of HTTP calls allows attackers to inject malicious code by intercepting or spoofing the device's internet connectivity checks performed over unsecured HTTP.
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.19.117CVSS 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.
-
Confirm device is Western Digital My Cloud NASAccess the device web interface or check the product label/model number to verify the device is a Western Digital My Cloud series NASAffected if Device is not a Western Digital My Cloud NAS - this CVE does not apply
-
Check installed firmware versionLog into the My Cloud dashboard, navigate to Settings > About or look for firmware version in the web UI footer. Alternatively, access the device via SSH and run: cat /etc/version or cat /mnt/boot/VERSIONAffected if Firmware version is 5.19.117 or higher - the vulnerability was patched in this version
-
Identify if HTTP connectivity check is enabledIn the My Cloud web interface, go to Settings > Network > Internet or Settings > Network > Connectivity Check. Look for an option related to internet connectivity checks and verify whether it uses HTTP (instead of HTTPS) or is enabled at allAffected if HTTP-based internet connectivity checks are enabled - this is the vulnerable configuration that allows code injection via man-in-the-middle attacks
A user is affected if they have a Western Digital My Cloud NAS running firmware versions prior to 5.19.117 AND have the HTTP-based internet connectivity check feature enabled on their device.
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.19.117
Update firmware to version that disables HTTP-based internet connectivity checks, or manually disable the HTTP connectivity check feature if present in device settings.
My Cloud OS 5.19.117 or later
- Upgrade the My Cloud OS firmware to version 5.19.117 or later via the device's web interface or management console
- After upgrading, verify the firmware version reflects 5.19.117 or higher in the device settings
- Confirm that the device no longer performs internet connectivity checks over HTTP
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22994 — 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-22994 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