CVE-2017-8146
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 call module of P10 and P10 Plus smartphones with software versions before VTR-AL00C00B167, versions before VTR-TL00C01B167, versions before VKY-AL00C00B167, versions before VKY-TL00C01B167 has a DoS vulnerability. An attacker may trick a user into installing a malicious application, and the application can send given parameter to call module to crash the call and data communication process.
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 confidenceA denial of service vulnerability exists in the call module of Huawei P10 and P10 Plus smartphones running software versions prior to the patched releases (VTR-AL00C00B167, VTR-TL00C01B167, VKY-AL00C00B167, VKY-TL00C01B167). An attacker can exploit this by tricking a user into installing a malicious application that sends a specific parameter to the call module, causing the call and data communication processes to crash.
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< vtr-al00c00b167< vtr-tl00c01b167< vky-al00c00b167< vky-tl00c01b167CVSS 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 your Huawei device modelGo to Settings > About Phone > Model Number to confirm whether you have a Huawei P10 (VTR-AL00, VTR-TL00) or P10 Plus (VKY-AL00, VKY-TL00)Affected if Device model is Huawei P10 or P10 Plus
-
Check your current firmware versionGo to Settings > About Phone > Version > Build Number or use *#*#2846579#*#* to access engineering menu, then navigate to Software Version to see the exact firmware build (such as VTR-AL00C00B167)Affected if Firmware version is below the patched releases for your model
-
Compare firmware against affected version thresholdsFor P10: compare your build against VTR-AL00C00B167 (AL00 variant) and VTR-TL00C01B167 (TL00 variant). For P10 Plus: compare against VKY-AL00C00B167 (AL00 variant) and VKY-TL00C01B167 (TL00 variant)Affected if Your firmware version is lower than the patched version for your specific model and variant
You are affected if you own a Huawei P10 or P10 Plus and your current firmware version is below the patched release for your specific model variant (VTR-AL00C00B167, VTR-TL00C01B167, VKY-AL00C00B167, or VKY-TL00C01B167).
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 dataApply the vendor-supplied firmware update from Huawei to patch the affected P10 and P10 Plus devices. Users should be instructed to only install applications from trusted sources to avoid triggering the malicious payload.
- Consultation3.0 h
- Implementation1.0 h
- Testing3.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 $2,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8146 — 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-8146 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