dbcve.org
My Cloud OsOperating system · Westerndigital

CVE-2023-22814

CRITICAL · 9.8 CVSS v3.1 Published 2023-07-01
Fix available
A fix is available. Upgrade to 5.26.202 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
An authentication bypass issue via spoofing was discovered in the token-based authentication mechanism that could allow an attacker to carry out an impersonation attack. This issue affects My Cloud OS 5 devices: 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 confidence

This is an authentication bypass vulnerability in My Cloud OS 5's token-based authentication mechanism. Attackers can exploit insufficient token validation to perform spoofing attacks, allowing them to impersonate legitimate users without proper credentials. The vulnerability exists in versions prior to 5.26.202.

MitigationUpgrade My Cloud OS 5 firmware to version 5.26.202 or later to patch the token validation vulnerability. If immediate patching is not possible, restrict network access to the device and monitor for unauthorized access attempts.

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.02.104, < 5.26.202

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
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 checks

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

  1. Identify My Cloud OS 5 device
    Log into the My Cloud device web interface and check the dashboard or settings page for the firmware version information. Alternatively, access the device via SSH and run: cat /etc/os-version or cat /mnt/boot/VERSION
    Affected if The device is running My Cloud OS 5 firmware
  2. Confirm firmware version
    Locate the firmware version displayed in the web UI under Settings > About or System > Firmware. In SSH, check: cat /etc/version or grep -i version /etc/os-release
    Affected if The displayed version matches 5.02.104 or higher but is below 5.26.202
  3. Verify token-based authentication is in use
    Check if remote access or cloud access features are enabled in the My Cloud OS 5 web interface under Settings > Cloud Access or Settings > Remote Access. These features utilize token-based authentication.
    Affected if Cloud Access or Remote Access features are enabled
  4. Check network exposure
    Review router/firewall settings to determine if the My Cloud device ports (80, 443, 8443) are exposed to the internet or accessible from untrusted networks.
    Affected if The device is directly accessible from external networks without VPN or firewall restrictions

The environment is affected if the My Cloud OS 5 firmware version falls within the range of 5.02.104 to 5.26.201 (inclusive) and remote/cloud access features are enabled.

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.26.202 or later
Fixed in 5.26.202
Interim mitigation

Upgrade My Cloud OS 5 firmware to version 5.26.202 or later to patch the token validation vulnerability. If immediate patching is not possible, restrict network access to the device and monitor for unauthorized access attempts.

Recommended fix High confidence

My Cloud OS version 5.26.202

  1. 1. Back up all critical data on the My Cloud device before performing any firmware update.
  2. 2. Download the latest My Cloud OS firmware version 5.26.202 or later from the official Western Digital support site.
  3. 3. Access the My Cloud dashboard through a web browser.
  4. 4. Navigate to Settings > Firmware Update or similar section.
  5. 5. Upload and apply the firmware update file.
  6. 6. Wait for the update process to complete and the device to reboot.
  7. 7. Verify the device is running version 5.26.202 or later by checking the firmware version in the settings.
Caveat Review Western Digital release notes for any configuration or feature changes between your current version and 5.26.202

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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