LiveActive security incident?Get immediate response
CVE Record

CVE-2017-15311: The baseband modules of Mate 10, Mate 10 Pro, Mate 9, Mate 9 Pro Huawei smart phones with software before A...

The baseband modules of Mate 10, Mate 10 Pro, Mate 9, Mate 9 Pro Huawei smart phones with software before ALP-AL00 8.0.0.120(SP2C00), before BLA-AL00 8.0.0.120(SP2C00), before MHA-AL00B 8.0.0.334(C00), and before LON-AL00B 8.0.0.334(C00) have a stack overflow vulnerability due to the lack of parameter validation. An attacker could send malicious packets to the smart phones within radio range by special wireless device, which leads stack overflow when the baseband module handles these packets. The attacker could exploit this vulnerability to perform a denial of service attack or remote code execution in baseband module.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2017-15311 affects specific Huawei Mate 9 and Mate 10 models. A nearby attacker using specialized wireless equipment could send malicious radio packets to the phone’s baseband processor, potentially causing service disruption or code execution inside the baseband. This is mainly a mobile-device exposure, not a typical internet-facing server risk. Exposure is limited to listed Huawei Mate 10, Mate 10 Pro, Mate 9, and Mate 9 Pro devices running vulnerable builds. Organizations with legacy Huawei mobile fleets, bring-your-own-device access, or high-risk travelers should check device inventories. Treat as a targeted mobile security concern. The attack requires proximity and specialized equipment, but possible baseband code execution raises impact for sensitive users. Prioritize confirming whether these older devices remain in use and updating or replacing them. Mitigation focus: Update affected Mate devices to the listed fixed build or later.; Check Huawei PSIRT guidance for model-specific update availability.; Retire or restrict devices that cannot receive the fixed software..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

description · low confidence lookup

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 lookup
cve · low confidence lookup

CVE-2017-15311 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Huawei Technologies Co., Ltd.Mate 10before ALP-AL00 8.0.0.120(SP2C00)Listed
Huawei Technologies Co., Ltd.Mate 10 Probefore BLA-AL00 8.0.0.120(SP2C00)Listed
Huawei Technologies Co., Ltd.Mate 9before MHA-AL00B 8.0.0.334(C00)Listed
Huawei Technologies Co., Ltd.Mate 9 Probefore LON-AL00B 8.0.0.334(C00),Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.