Unauthenticated device reboot via type confusion
Published Oct 11, 2023 · Updated Sep 18, 2024
Type confusion in Huawei HarmonyOS and EMUI distributed file modules allows remote attackers to force devices running listed releases to reboot. Huawei identifies the locus as the distributed file module but has not published which resource is accessed under an incompatible type. Exploitation requires network reachability but no privileges or user interaction; the reported consequence is a reboot without data access or modification.
Summary
What happened
Type confusion in Huawei HarmonyOS and EMUI distributed file modules allows remote attackers to force devices running listed releases to reboot. Huawei identifies the locus as the distributed file module but has not published which resource is accessed under an incompatible type. Exploitation requires network reachability but no privileges or user interaction; the reported consequence is a reboot without data access or modification.
The record
- CVE
- CVE-2023-44108
- Published
- Oct 11, 2023
- Updated
- Sep 18, 2024
- Vendor
- Huawei Technologies Co., Ltd.
- Product
- HarmonyOS
- Classifications
- CWE-843, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 11, 2023CVE publishedPublication date reported by the CVE source.
- Sep 18, 2024Record 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.0
- Affected versionversion=2.0.1
- Affected versionversion=2.1.0
- Affected versionversion=3.0.0
- Affected versionversion=3.1.0
- Affected versionversion=4.0.0
What conditions does exploitation require?
What is affected?
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