dbcve.org
P9 Plus FirmwareOperating system · Huawei

CVE-2017-2711

MEDIUM · 5.5 CVSS v3.0 Published 2017-11-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 · unedited
P9 Plus smartphones with software earlier than VIE-AL10C00B352 versions have an input validation vulnerability in the touchscreen Driver. An attacker can tricks a user into installing a malicious application on the smart phone, and send given parameter to smart phone to crash the system.

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 · moderate confidence

Input validation vulnerability in the touchscreen driver of Huawei P9 Plus smartphones running software versions earlier than VIE-AL10C00B352. A malicious application installed on the device can send a specific parameter to trigger a system crash.

MitigationUpdate Huawei P9 Plus software to version VIE-AL10C00B352 or later to patch the input validation vulnerability in the touchscreen driver.

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
P9 Plus FirmwareOperating system
Affected:< vie-al10c00b352

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device model is Huawei P9 Plus
    Check the device model number in Settings > About Phone > Model Number, or run 'getprop ro.product.model' via ADB shell
    Affected if Device model is not Huawei P9 Plus (VIE-AL10) - this CVE only affects that specific model
  2. Check firmware version against affected range
    Navigate to Settings > About Phone > Version number, or run 'getprop ro.build.version.emui' and 'getprop ro.build.display.id' via ADB shell
    Affected if Firmware version is earlier than VIE-AL10C00B352 (e.g., VIE-AL10C00B340, VIE-AL10C00B300, etc.)
  3. Verify touchscreen driver is active
    Check if the touchscreen input device is present and functional by running 'getevent -l' via ADB shell and looking for event streams from touchscreen (typically /dev/input/event1), or check 'cat /proc/bus/input/devices' for an attached touchscreen driver
    Affected if Touchscreen driver is not loaded or not present - the vulnerability requires an active touchscreen driver to be exploitable

Device is affected if it is a Huawei P9 Plus (VIE-AL10) running firmware versions earlier than VIE-AL10C00B352 and has an active touchscreen driver.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Huawei P9 Plus software to version VIE-AL10C00B352 or later to patch the input validation vulnerability in the touchscreen driver.

Fix this in P9 Plus Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-2711 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-2711 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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