CVE-2017-15325
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceInteger overflow vulnerability in the Bdat driver of Huawei Prague smartphones due to lack of parameter validation. An attacker can exploit this by tricking a user into installing a malicious app that sends specially crafted parameters to the driver, achieving arbitrary code execution with elevated privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< prague-al00ac00b211< prague-al00bc00b211< prague-al00cc00b211< prague-tl00ac01b211< prague-tl10ac01b211CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device modelCheck the device model number in Settings > About Phone. Look for model identifiers: Al00a, Al00b, Al00c, Tl00a, or Tl10a.Affected if Device model is one of the listed Huawei Prague variants (Al00a, Al00b, Al00c, Tl00a, Tl10a)
-
Check firmware versionNavigate to Settings > About Phone > Version. Identify the build number (for example, prague-al00ac00bXXX where XXX is the build version).Affected if Firmware version is earlier than B211 (for example, prague-al00ac00b210 or earlier)
-
Verify Bdat driver presenceCheck if the Bdat driver is present on the device by examining /system/lib/modules/bdat.ko or by checking driver loaded status via 'lsmod | grep bdat' if root access is available.Affected if Bdat driver is loaded or present on the device
-
Confirm vulnerable parameter interfaceIf root access is available, verify the Bdat driver exposes a parameter interface by checking /sys/class/misc/bdat/ or similar driver nodes. The vulnerability requires the driver to accept userland parameters.Affected if Bdat driver interface is accessible and accepts parameters from applications
You are affected if you own a Huawei Prague model (Al00a, Al00b, Al00c, Tl00a, Tl10a) and your firmware version is earlier than B211, with the Bdat driver loaded and accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Huawei Prague smartphones to software version B211 or later. Users should avoid installing applications from untrusted sources to prevent initial access.
- Consultation4.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15325 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-15325 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data