Availability impact via Settings.Secure tampering
Published Apr 11, 2022 · Updated Aug 4, 2024
An authorization vulnerability in Huawei HarmonyOS 2.0 allows remote attackers to affect availability via multi-window Settings.Secure tampering. The multi-window module can insert and alter Settings.Secure values without authorization. Huawei does not disclose the required entry point or privilege gate, and the reported consequence is limited to possible system-availability impact.
Summary
What happened
An authorization vulnerability in Huawei HarmonyOS 2.0 allows remote attackers to affect availability via multi-window Settings.Secure tampering. The multi-window module can insert and alter Settings.Secure values without authorization. Huawei does not disclose the required entry point or privilege gate, and the reported consequence is limited to possible system-availability impact.
The record
- CVE
- CVE-2021-46742
- Published
- Apr 11, 2022
- Updated
- Aug 4, 2024
- Vendor
- Huawei Technologies Co., Ltd.
- Product
- HarmonyOS
- Classifications
- T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 11, 2022CVE 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.
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