LiveActive security incident?Get immediate response
CVE Record

CVE-2017-8204: The Bastet driver of Honor 9 Huawei smart phones with software of versions earlier than Stanford-AL10C00B17...

The Bastet driver of Honor 9 Huawei smart phones with software of versions earlier than Stanford-AL10C00B175 has a buffer overflow vulnerability due to the lack of parameter validation. An attacker tricks a user into installing a malicious APP which has the root privilege; the APP can send a specific parameter to the driver of the smart phone, causing arbitrary code execution

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2017-8204 affects the Bastet driver on Huawei Honor 9 phones running software earlier than Stanford-AL10C00B175. A malicious app with root privilege can pass unsafe input to the driver and trigger arbitrary code execution. Business urgency is mainly for organizations still managing these legacy devices. Exposure appears limited to Huawei Honor 9 devices on versions earlier than Stanford-AL10C00B175. Organizations without this model, without rooted devices, or without legacy Huawei mobile fleets are unlikely to be affected based on the provided sources. Treat this as a legacy mobile fleet hygiene issue. Prioritize if Honor 9 devices remain in use for corporate access, especially if rooting or unmanaged app installation is possible. Otherwise, business urgency is limited. Mitigation focus: Identify any Honor 9 devices running versions earlier than Stanford-AL10C00B175.; Update affected devices to Stanford-AL10C00B175 or later if available from Huawei.; Review Huawei PSIRT guidance before relying on compensating controls..

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-8204 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.Honor 9Versions earlier than Stanford-AL10C00B175Listed
Weakness

CWE details

No CWE listed

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