CVE-2017-17313
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 inputhub driver of HUAWEI P9 Lite mobile phones with Versions earlier than VNS-L21C02B341, Versions earlier than VNS-L21C22B380, Versions earlier than VNS-L31C02B341, Versions earlier than VNS-L31C440B390, Versions earlier than VNS-L31C636B396 has a buffer overflow vulnerability due to the lack of parameter validation. An attacker tricks a user into installing a malicious APP and the APP may sends specific data to the inputhub driver to exploit this vulnerability, successful exploit could cause the system reboot.
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 confidenceA buffer overflow vulnerability exists in the inputhub driver of Huawei P9 Lite mobile phones (VNS-L21 and VNS-L31 variants) due to insufficient parameter validation. An attacker can exploit this by tricking users into installing a malicious application that sends crafted data to the inputhub driver, causing a system reboot.
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< vns-l31c02b341< vns-l21c22b380< vns-l31c440b390< vns-l31c636b396CVSS 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 the device settings under 'About Phone' > 'Model Number' or run 'getprop ro.product.model' via ADB shellAffected if Model is not VNS-L21 or VNS-L31 (not a Huawei P9 Lite) - the device is not affected
-
Check firmware version for VNS-L21 variantCheck build number in 'About Phone' > 'Build Number' or run 'getprop ro.build.display.id' via ADB shell. Compare against affected versions: any build below vns-l21c22b380Affected if Build number is less than vns-l21c22b380 - device is affected
-
Check firmware version for VNS-L31 variantCheck build number in 'About Phone' > 'Build Number' or run 'getprop ro.build.display.id' via ADB shell. Compare against all three affected version ranges: below vns-l31c02b341, below vns-l31c440b390, or below vns-l31c636b396Affected if Build number is less than any of these thresholds (vns-l31c02b341, vns-l31c440b390, vns-l31c636b396) - device is affected
-
Verify inputhub driver presenceCheck if the inputhub driver is accessible by examining /dev/inputhub or running 'ls -la /dev/inputhub*' via ADB shell with root accessAffected if Driver exists and is accessible - the vulnerable component is present on the device
Device is affected only if it is a Huawei P9 Lite VNS-L21 or VNS-L31 variant running firmware build numbers below the patched thresholds AND the inputhub driver is present on the device.
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 dataUsers should update their device firmware to the patched versions (VNS-L21C02B341, VNS-L21C22B380, VNS-L31C02B341, VNS-L31C440B390, VNS-L31C636B396 or later). Enterprises should inventory affected devices and ensure update mechanisms are in place.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-17313 — 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-17313 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