Kernel crash via improperly validated input
Published Nov 23, 2021 · Updated Aug 4, 2024
Improper input validation in Huawei HarmonyOS 2.0 allows remote attackers to crash the smartphone kernel through unspecified input. Huawei has not disclosed the affected component or how it mishandles untrusted input before the kernel crash. No authentication or user interaction is required, but the undisclosed input path limits exposure assessment.
Summary
What happened
Improper input validation in Huawei HarmonyOS 2.0 allows remote attackers to crash the smartphone kernel through unspecified input. Huawei has not disclosed the affected component or how it mishandles untrusted input before the kernel crash. No authentication or user interaction is required, but the undisclosed input path limits exposure assessment.
The record
- CVE
- CVE-2021-37003
- Published
- Nov 23, 2021
- Updated
- Aug 4, 2024
- Vendor
- Huawei Technologies Co., Ltd.
- Product
- HarmonyOS
- Classifications
- CWE-20, T1642
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 23, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
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.
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