CVE-2017-8172
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 · uneditedIsub service in P10 Plus and P10 smart phones with earlier than VKY-AL00C00B157 versions and earlier than VTR-AL00C00B157 versions has a denial of service (DoS) vulnerability. An attacker tricks a user into installing a malicious application on the smart phone, and the application can send given parameter to specific interface, which make a out-of-bounds array access that results in smart phone restart.
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 confidenceOut-of-bounds array access vulnerability in the Isub service on Huawei P10 and P10 Plus smartphones allows a locally-installed malicious application to send a crafted parameter to a specific interface, triggering a buffer overflow that causes device restart (DoS).
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< vky-al00c00b157< vtr-al00c00b157CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 if the device is Huawei P10 or Huawei P10 Plus. On the device, go to Settings > About Phone > Model Number, or run 'getprop ro.product.model' via ADB shell.Affected if Device model is not Huawei P10 (model number VTR-AL00) or Huawei P10 Plus (model number VKY-AL00)
-
Check firmware version for P10For Huawei P10, check the build number in Settings > About Phone > Build Number, or run 'getprop ro.build.version.emui' and 'getprop ro.build.display.id' via ADB shell. Compare the version to vtr-al00c00b157.Affected if Firmware version is earlier than VTR-AL00C00B157 (e.g., VTR-AL00C00, VTR-AL00x versions before C00B157)
-
Check firmware version for P10 PlusFor Huawei P10 Plus, check the build number in Settings > About Phone > Build Number, or run 'getprop ro.build.version.emui' and 'getprop ro.build.display.id' via ADB shell. Compare the version to vky-al00c00b157.Affected if Firmware version is earlier than VKY-AL00C00B157 (e.g., VKY-AL00C00, VKY-AL00x versions before C00B157)
-
Verify Isub service presenceCheck if the Isub service is running on the device. Run 'dumpsys' or check for the Isub-related processes via ADB shell with 'ps -A | grep -i isub' or by examining system service list.Affected if Isub service is present and running on the device
A user is affected if they own a Huawei P10 (before VTR-AL00C00B157) or P10 Plus (before VKY-AL00C00B157) device with the Isub service enabled.
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 device firmware to VKY-AL00C00B157 or later (P10 Plus) and VTR-AL00C00B157 or later (P10) to patch the Isub service vulnerability. Additionally, enforce policies restricting app installation to trusted sources to prevent exploitation.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8172 — 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-8172 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