Security readout for executives and security teams
Plain-English summary
CVE-2021-46895 is a Huawei HarmonyOS/EMUI issue in the Multi-Device Task Center. The reported impact is that a hopped app can bypass app lock and reset the device that initiated the hop. Public severity, CVSS score, affected models, and remediation details are not provided in the source bundle.
Executive priority
Track this as a Huawei mobile/device-management risk with incomplete public severity data. Prioritize validation where Huawei devices handle sensitive apps or are managed in enterprise fleets, but avoid escalation claims without vendor or exploitation evidence.
Technical view
The CVE describes a design-process defect classified as CWE-701 affecting Huawei HarmonyOS 2.0.0 and EMUI 12.0.0. Successful exploitation affects app-lock enforcement during Multi-Device Task Center hopping and can trigger a reset of the initiating device. The sources do not provide attack prerequisites, CVSS metrics, patches, or proof-of-concept details.
Likely exposure
Exposure appears limited to Huawei environments using HarmonyOS 2.0.0 or EMUI 12.0.0 with Multi-Device Task Center app hopping. The bundle does not identify specific device models, regions, builds, or enterprise management conditions.
Exploitation context
The source bundle does not report active exploitation, public exploit availability, or CISA KEV listing. It only states the successful-exploitation impact. Treat exploitability details as incomplete rather than confirmed low risk.
Researcher notes
Key missing data: CVSS vector, affected build ranges, model list, prerequisites, patch identifiers, and exploit status. The impact combines app-lock bypass with device reset behavior, so validation should focus on supported-version mapping and vendor bulletin correlation, not independent exploit reproduction.
Mitigation direction
- Check Huawei August 2023 security bulletins for vendor remediation guidance.
- Update affected HarmonyOS and EMUI devices through supported vendor channels.
- Review enterprise policies for Multi-Device Task Center usage on sensitive devices.
- Do not infer fixes or affected models beyond Huawei’s published guidance.
Validation and detection
- Inventory Huawei devices running HarmonyOS 2.0.0 or EMUI 12.0.0.
- Identify devices where Multi-Device Task Center or app hopping is enabled.
- Confirm current security patch level against Huawei’s August 2023 bulletin.
- Document any unsupported devices requiring risk acceptance or replacement.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-701: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-46895 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Weaknesses Introduced During Design
Weaknesses Introduced During Design represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.