LiveActive security incident?Get immediate response
CVE Record

CVE-2017-15325: The Bdat driver of Prague smart phones with software versions earlier than Prague-AL00AC00B211, versions ea...

The Bdat driver of Prague smart phones with software versions earlier than Prague-AL00AC00B211, versions earlier than Prague-AL00BC00B211, versions earlier than Prague-AL00CC00B211, versions earlier than Prague-TL00AC01B211, versions earlier than Prague-TL10AC01B211 has integer overflow vulnerability due to the lack of parameter validation. An attacker tricks a user into installing a malicious APP and execute it as a specific privilege; the APP can then 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

This is a Huawei Prague smartphone driver flaw. A malicious app, if installed and run with the required privilege, could trigger integer overflow behavior in the Bdat driver and lead to arbitrary code execution. The issue affects listed firmware versions earlier than the B211 builds. Exposure appears limited to Huawei Prague smartphones running firmware earlier than Prague-AL00AC00B211, AL00BC00B211, AL00CC00B211, TL00AC01B211, or TL10AC01B211. Enterprise exposure is mainly legacy or unmanaged BYOD devices still using those builds. Treat this as a targeted legacy mobile-device risk. Prioritize inventory and update confirmation if Huawei Prague devices are present. If none are in use, document non-exposure and monitor only for asset drift. Mitigation focus: Inventory Huawei Prague devices and record exact firmware build strings.; Update affected devices to the relevant B211 or later firmware build.; Restrict installation of untrusted apps on affected or unmanaged devices..

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-15325 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.PragueVersions earlier than Prague-AL00AC00B211, Versions earlier than Prague-AL00BC00B211, Versions earlier than Prague-AL00CC00B211, Versions earlier than Prague-TL00AC01B211, Versions earlier than Prague-TL10AC01B211Listed
Weakness

CWE details

No CWE listed

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