CVE-2017-8143
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 · uneditedWi-Fi driver of Honor 5C and P9 Lite Huawei smart phones with software versions earlier than NEM-L21C432B351 and versions earlier than VNS-L21C10B381 has a DoS vulnerability. An attacker may trick a user into installing a malicious application and the application can access invalid address of driver 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 confidenceA denial of service vulnerability exists in the Wi-Fi driver of Honor 5C and P9 Lite Huawei smartphones. An attacker can trick a user into installing a malicious application that accesses an invalid memory address in the Wi-Fi driver, causing the system 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< nem-l21c432b351< vns-l21c10b381CVSS 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 device modelGo to Settings > About Phone on your Huawei smartphone and confirm the model name. Look specifically for 'Honor 5C' or 'P9 Lite'.Affected if Your device is NOT an Honor 5C or P9 Lite, then you are not affected by this specific CVE.
-
Determine your firmware version for Honor 5COn Honor 5C, go to Settings > About Phone > Version. Look for the build number (e.g., NEM-L21). Compare your full firmware version against 'nem-l21c432b351'.Affected if You are running an Honor 5C with firmware version earlier than NEM-L21C432B351.
-
Determine your firmware version for P9 LiteOn P9 Lite, go to Settings > About Phone > Version. Look for the build number (e.g., VNS-L21). Compare your full firmware version against 'vns-l21c10b381'.Affected if You are running a P9 Lite with firmware version earlier than VNS-L21C10B381.
-
Confirm Wi-Fi driver is in useVerify that Wi-Fi functionality is enabled on your device. Go to Settings > Wi-Fi and ensure Wi-Fi is turned on. The vulnerability triggers when a malicious app accesses the Wi-Fi driver.Affected if Wi-Fi is enabled on a vulnerable firmware version.
You are affected if you own an Honor 5C or P9 Lite running firmware below NEM-L21C432B351 or VNS-L21C10B381 respectively, and you have Wi-Fi 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 the patched versions (NEM-L21C432B351 or later for NEM-L21, VNS-L21C10B381 or later for VNS-L21) and avoid installing applications from untrusted sources.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.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,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8143 — 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-8143 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