Security readout for executives and security teams
Plain-English summary
CVE-2021-46852 is a Huawei HarmonyOS and EMUI vulnerability in a memory management module. The published impact is loss of data confidentiality. It is rated high because the CVSS vector says it can be reached over a network without authentication or user interaction.
Executive priority
Prioritize this for Huawei mobile fleets because the rated impact is high confidentiality loss and no authentication is required. Urgency depends on whether affected OS versions are still present and whether those devices access sensitive business data.
Technical view
The source describes a logic bypass in the memory management module, mapped to CWE-306. Affected products are Huawei HarmonyOS 2.0 and EMUI 12.0.0. CVSS 3.1 is 7.5 with AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
Likely exposure
Exposure is limited to environments with Huawei devices running HarmonyOS 2.0 or EMUI 12.0.0. The source bundle does not identify affected device models, fixed build numbers, or configuration-dependent exposure conditions.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. It also does not include public exploit evidence. Treat this as a high-severity confidentiality issue, but do not claim exploitation without new vendor or KEV evidence.
Researcher notes
Evidence is sparse: the bundle provides CVE metadata, affected OS versions, CVSS, CWE-306, and Huawei bulletin references. It does not provide root-cause detail, exploit primitives, proof-of-concept status, affected models, or fixed build identifiers.
Mitigation direction
- Inventory Huawei devices running HarmonyOS or EMUI.
- Check Huawei November 2022 bulletins for vendor update guidance.
- Prioritize updates for HarmonyOS 2.0 and EMUI 12.0.0 devices.
- Retire or isolate devices that cannot receive supported updates.
- Monitor Huawei advisories for fixed build or device-specific details.
Validation and detection
- Confirm device OS family and exact version.
- Compare device patch level with Huawei bulletin guidance.
- Identify business systems accessed from affected Huawei devices.
- Check MDM or asset records for unsupported Huawei builds.
- Document any devices awaiting vendor-confirmed remediation.
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-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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-46852 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
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.