Service disruption via unverified recovery update package
Published Aug 9, 2022 · Updated Mar 6, 2026
Update verification bypass in Huawei HarmonyOS 2.0 and EMUI 11.0.0, 11.0.1, and 12.0.0 allows remote attackers to disrupt service. The recovery module accepts an update package for use without first verifying its authenticity, allowing invalid package data to enter the recovery path. No privileges or user interaction are required; published details establish a network path and high availability impact but do not specify whether exploitation causes a crash, hang, or reboot.
Summary
What happened
Update verification bypass in Huawei HarmonyOS 2.0 and EMUI 11.0.0, 11.0.1, and 12.0.0 allows remote attackers to disrupt service. The recovery module accepts an update package for use without first verifying its authenticity, allowing invalid package data to enter the recovery path. No privileges or user interaction are required; published details establish a network path and high availability impact but do not specify whether exploitation causes a crash, hang, or reboot.
The record
- CVE
- CVE-2022-37008
- Published
- Aug 9, 2022
- Updated
- Mar 6, 2026
- Vendor
- Huawei Technologies Co., Ltd.
- Product
- HarmonyOS
- Classifications
- CWE-345
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 9, 2022CVE publishedPublication date reported by the CVE source.
- Mar 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo