Security readout for executives and security teams
Plain-English summary
CVE-2021-22367 is a key management error in Huawei smartphone software. If exploited, it may let an attacker bypass authentication. The public bundle does not provide a severity score, attack prerequisites, affected device models, or confirmed exploitation evidence.
Executive priority
Treat this as an inventory and patch governance issue for Huawei smartphone fleets. Business urgency depends on whether affected devices handle sensitive access, but the public evidence is too incomplete to rate severity confidently.
Technical view
The CVE describes a key management error affecting listed EMUI and Magic UI versions. The documented impact is potential authentication bypass. Available sources do not name a CWE, CVSS vector, proof of exploitation, vulnerable component, or exact remediation build.
Likely exposure
Exposure is most likely on Huawei smartphones running the listed EMUI 9.1.x through 11.0.0 versions or Magic UI 2.1.1 through 4.0.0. Model-level exposure is not provided in the bundle.
Exploitation context
No CISA KEV listing or cited source in the bundle indicates active exploitation. The sources only state that successful exploitation may lead to authentication bypass, without technical conditions or exploit maturity.
Researcher notes
Key missing data includes CVSS, CWE, vulnerable subsystem, attack vector, privileges required, user interaction, affected models, and fixed builds. Analysis should stay anchored to vendor bulletin data and local device build evidence.
Mitigation direction
- Inventory Huawei smartphones and record EMUI or Magic UI versions.
- Review Huawei's May 2021 security bulletin for vendor guidance.
- Apply available vendor security updates through supported management channels.
- Prioritize unsupported or unmanaged phones for replacement or isolation.
- Avoid assuming a fix level not confirmed by Huawei documentation.
Validation and detection
- Confirm whether any devices run the listed EMUI or Magic UI versions.
- Compare device builds against Huawei's May 2021 bulletin guidance.
- Document devices with no available vendor update path.
- Verify mobile device management compliance reporting covers OS build versions.
- Track exceptions until patched, retired, or formally risk-accepted.
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.
Credential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-22367 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
- CVE List V5 sourceCVE List V5
- https://consumer.huawei.com/en/support/bulletin/2021/5/CVE reference · x_refsource_MISC
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.