Security readout for executives and security teams
CVE-2017-2692 affects Huawei’s Keyguard application on several older Huawei and Honor phone firmware lines. The issue can allow privilege elevation through command injection, meaning a successful attacker could move beyond normal app permissions on an affected device. Exposure is most likely in organizations still using or supporting the listed Huawei and Honor devices, including BYOD, field-service phones, test devices, or unmanaged legacy handsets running affected firmware builds. Treat this as a high-priority legacy mobile exposure where affected devices access company data. Urgency depends on whether matching firmware remains in use, because the sources do not confirm active exploitation or provide exploit maturity details. Mitigation focus: Inventory Huawei and Honor devices against the affected model and firmware list.; Check Huawei PSIRT guidance for fixed firmware or vendor-approved updates.; Retire or isolate devices that cannot receive supported firmware updates..
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.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2017-2692 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
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.