CVE-2022-22994: Insufficient Verification of Data Authenticity Remote Code Execution Vulnerability on Western Digital My Cloud devices.
Noroxi assessment
Priority: Plan (action score 40/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.8% (FIRST EPSS); higher than 79% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Add it to your regular patch cycle. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A 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.
- Published
- Jan 28, 2022
- Updated
- Jun 17, 2026
- EPSS
- 1.8% · 79th percentile
- CWE
- CWE-345
Report tools
Action score
40
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.8%
CNA vs NVD score
- NVD
- 9.8
- CNA · WDC PSIRT
- 8.8
- 1.0 point gap
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| westerndigital | my cloud os | cpe:2.3:o:westerndigital:my_cloud_os |
| westerndigital | my cloud | cpe:2.3:h:westerndigital:my_cloud |
| westerndigital | my cloud dl2100 | cpe:2.3:h:westerndigital:my_cloud_dl2100 |
| westerndigital | my cloud dl4100 | cpe:2.3:h:westerndigital:my_cloud_dl4100 |
| westerndigital | my cloud ex2 ultra | cpe:2.3:h:westerndigital:my_cloud_ex2_ultra |
| westerndigital | my cloud ex2100 | cpe:2.3:h:westerndigital:my_cloud_ex2100 |
| westerndigital | my cloud ex4100 | cpe:2.3:h:westerndigital:my_cloud_ex4100 |
| westerndigital | my cloud mirror gen 2 | cpe:2.3:h:westerndigital:my_cloud_mirror_gen_2 |
| westerndigital | my cloud pr2100 | cpe:2.3:h:westerndigital:my_cloud_pr2100 |
| westerndigital | my cloud pr4100 | cpe:2.3:h:westerndigital:my_cloud_pr4100 |
| westerndigital | wd cloud | cpe:2.3:h:westerndigital:wd_cloud |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- westerndigital my cloud osbefore 5.19.117
Versions reported by the vendor
Affected version ranges reported by the assigning authority (WDC PSIRT). Independent of NVD's CPE analysis and usually ahead of it.
Western Digital My Cloud
- My Cloud OS 5 and later · before 5.19.117affected
Same product
westerndigital: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-29842Command Injection Vulnerability in Western Digital My Cloud devices40Plan
- CVE-2022-22992Command Injection Remote Code Execution vulnerability on Western Digital My Cloud devices.40Plan
- CVE-2023-22814Authentication Bypass issue in My Cloud OS 5 devices39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2022-22991Jan 13, 2022 · Command injection through unsecured HTTP calls on Western Digital My Cloud devices35Monitor
- ← EarlierCVE-2022-22993Jan 28, 2022 · Limited Server-Side Request Forgery vulnerability on Western Digital My Cloud devices.35Monitor
- Later →CVE-2022-29838Dec 9, 2022 · Authentication issue with the encrypted volumes and auto mount feature in My Cloud devices18Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-345 · Insufficient Verification of Data AuthenticityCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- JSON Hijacking (aka JavaScript Hijacking)CAPEC-111likelihood: High · High
- Cache PoisoningCAPEC-141likelihood: High · High
- DNS Cache PoisoningCAPEC-142likelihood: High · High
- Content SpoofingCAPEC-148likelihood: Medium · Medium
- Spoofing of UDDI/ebXML MessagesCAPEC-218Medium
- Application API Message Manipulation via Man-in-the-MiddleCAPEC-384Low
- Transaction or Event Tampering via Application API ManipulationCAPEC-385Medium
- Application API Navigation RemappingCAPEC-386Medium
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.